Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site drux3.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!drutx!drux3!pcf
From: pcf@drux3.UUCP (FryPC)
Newsgroups: net.lang
Subject: Re: Operator Precedence
Message-ID: <1363@drux3.UUCP>
Date: Sat, 21-Sep-85 17:56:52 EDT
Article-I.D.: drux3.1363
Posted: Sat Sep 21 17:56:52 1985
Date-Received: Sun, 22-Sep-85 06:28:42 EDT
References: <262@pedsgd.UUCP> <1502@umcp-cs.UUCP>, <205@graffiti.UUCP>
Organization: AT&T Information Systems Laboratories, Denver
Lines: 34

>> Another interesting(?) idea would be to base operator binding on
>> spacing: 

> I'd hate to program in that, but that's certainly an interesting idea. Then
> you could indicate compound and continued statements by indentation:
> Any programming languages actually do this, by the way?

Yes, occam, the concurrent language developed by Inmos does just that. They
justify it on two grounds: firstly, most people make mistekes (sic) by 
forgetting braces rather than forgetting to indent; and secondly, most
terminals only have 24 lines and you shouldn't waste them. 

To mess with your example:
(Note that the 'if' performs the code after the first 'true' condition so
that it can also act as a 'switch' statement, and 'true' acts as an 'else'
statement.)

   if
      a < b
         blah;
         blah;
      a < c
	 on the other hand;
      true
         while \ finished
            this;
            and that;
            and the other thing;

      etc.;


Peter Fry
drux3!pcf


Brought to you by Super Global Mega Corp .com