Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!icdoc!inmos!inmos-c!chris
From: chris@inmos.COM (Chris Larsen)
Newsgroups: comp.lang.misc
Subject: Re: Anyone want to design a languag
Message-ID: <1990Feb26.220947.1199@inmos.COM>
Date: 26 Feb 90 22:09:47 GMT
References: <1944@l.cc.purdue.edu> <7300007@ux1.cso.uiuc.edu> <15190@bfmny0.UU.NET>
Sender: Chris Larsen
Organization: INMOS Corporation, Colorado Springs
Lines: 18

In article <15190@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes:
>Wouldn't depth-by-indentation make include files a nightmare?

Not neccesarily.  occam, Inmos' language designed for parallel processing,
uses include files and indentation is part of the language's syntax.
"Unindenting" causes the end of scope for items declared at the previous
level of indentation.  Using include files can be quite a useful tool to
simulate record structures in occam since occam doesn't have record
structures.

The way the mechanism is controlled is that the #INCLUDE statement in occam
is indented to the level the programmer wishes the include file contents
indented to.  This means that generally speaking, there should be no
indentation in the include file itself!

Chris Larsen
chris@isnet.inmos.COM
Inmos US Central Apps./US Software Support