Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!mcvax!ukc!stc!inset!mikeb
From: mikeb@inset.UUCP (Mike Banahan)
Newsgroups: net.lang.c
Subject: Re: Indentation
Message-ID: <995@inset.UUCP>
Date: Tue, 13-May-86 13:53:21 EDT
Article-I.D.: inset.995
Posted: Tue May 13 13:53:21 1986
Date-Received: Thu, 15-May-86 06:46:32 EDT
References: <501@brl-smoke.ARPA> <797@bentley.UUCP>
Reply-To: mikeb@inset.UUCP (Mike Banahan)
Organization: The Instruction Set Ltd., London, UK.
Lines: 28

In article <797@bentley.UUCP> kwh@bentley.UUCP writes:
(I just pull out the bit that interests me)

>In article <501@brl-smoke.ARPA> rbj@icst-cmr (Root Boy Jim) writes:
>>I have ranted about C using a one statement model for its control
>>statements instead of an explicit end statement.  Compound statements are
>>bounded by braces instead.  Yuk!
>
>Ah yes, there are two major types of language in the structured family;
>f77 with "endif" (some members use "end" for all of "endif", "endwhile",
>etc.) and pascal with "begin" "end" (which C abbreviates to "{" "}").  I
>presume this is what you dislike.  (If it's the spelling that bothers you,
>I'm sure you're aware that you can define "begin" and "end" as macros.)
>
>Yet another convention, not endorsed by any language I know, is to dispense
>with the braces and let the indentation alone tell the compiler how to
>interpret the program.  (I came up with this idea after an argument on the
>"correct" place to put the braces.)

Sorry, you're wrong. Occam uses indentation to show nesting. You *can't*
write an incorrectly indented program, because different indent is a different
program!

(Occam is the parallel language for the Inmos Transputer; it's good fun
but boy do you have to re-think those old ideas about sequential execution.)
-- 
Mike Banahan, Technical Director, The Instruction Set Ltd.
mcvax!ukc!inset!mikeb