Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 8/23/84; site ucbcad.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ucbvax!ucbcad!rudell
From: rudell@ucbcad.UUCP
Newsgroups: net.lang.c
Subject: Re: Re: Multilevel standards
Message-ID: <52@ucbcad.UUCP>
Date: Tue, 8-Jan-85 17:41:47 EST
Article-I.D.: ucbcad.52
Posted: Tue Jan  8 17:41:47 1985
Date-Received: Fri, 11-Jan-85 23:23:55 EST
References: <4859@utzoo.UUCP> <11@mit-athena.ARPA> <177@gcc-opus.ARPA>
Organization: UC Berkeley CAD Group, Berkeley, CA
Lines: 27

> Ah John, perhaps you should have a short talk with the folks over at Apollo.
> They built an entire os, a transparent shared file system, network and
> graphics system using Pascal. It has dynamic runtime binding (unlike unix)
> and shared runtime libraries (unlike unix).
> The system is not shabby - it's real fast AND supports C.
> 
> Not bad for a "toy language". 
> 
> (personally, I would have done the work in C, but it shows that that vehicle
>  is not the only concideration, the destination is...)
> 
> -- 
> 
> J Bradford Parker


Wait one minute.  You can hardly call what Apollo used standard
Pascal.  It is a language which will run on no other machine.  They
essentially added many C-like constructs (free pointers, a notion of
modularity (they even call them static and extern!) to the syntax of
Pascal.  The argument was that Standard Pascal is a toy language.
Apollo Pascal is a real language, but unfortunately, no one but Apollo
uses it.

Sure, a "standard" Pascal program will get close to running on the Apollo
(assuming you never try to open a file given a specific filename, or
binary search an enumerated-type :-)