Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site leadsv.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!cae780!leadsv!horst
From: horst@leadsv.UUCP (John Selhorst)
Newsgroups: net.lang
Subject: Re: Operator Precedence
Message-ID: <624@leadsv.UUCP>
Date: Mon, 23-Sep-85 15:17:30 EDT
Article-I.D.: leadsv.624
Posted: Mon Sep 23 15:17:30 1985
Date-Received: Fri, 27-Sep-85 07:44:58 EDT
References: <262@pedsgd.UUCP> <1502@umcp-cs.UUCP> <205@graffiti.UUCP>
Organization: LMSC-LEADS, Sunnyvale, Ca.
Lines: 38
Summary: see Occam.

In article <205@graffiti.UUCP>, peter@graffiti.UUCP (Peter da Silva) writes:
> I'd hate to program in that, but that's certainly an interesting idea. Then
> you could indicate compound and continued statements by indentation:
> 
> 	if a < b
> 	  blah
> 	  blah
> 	else
> 	  while not finished
> 	    do this,
> 	      and that
> 	      and the other thing
> 	    remember to reinit the loop!
> 	and in any case...
> 
> Any programming languages actually do this, by the way?

Yes, take a look at Occam. It's been a while since I've looked at it, but
remember something very much like that. I don't find it very easy to read
but with a little adaptation it might be quite usable. A major advantage
is that all of the implementations I've heard of include a syntax-directed
text editor which makes writing like that much easier - you don't have to
space over on every line. Occam also has some other nifty stuff you might
want to check out. It was developed by Inmos and is used with their
Transputer.

(The above was probably written by someone else illicitly logged into my
 account. But send me mail anyway, as s/he will probably end up reading
 it anyway.)

John Selhorst
 {(ucbvax!dual!sun) (ihnp4!qubix)}!sunncal!leadsv!horst
 {{allegra ihnp4 dual}!fortune decvax!decwrl}!amdcad!cae780!leadsv!horst


-- 
 {(ucbvax!dual!sun) (ihnp4!qubix)}!sunncal!leadsv!horst
 {{allegra ihnp4 dual}!fortune decvax!decwrl}!amdcad!cae780!leadsv!horst