Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!helios.ee.lbl.gov!nosc!trout.nosc.mil!broman From: broman@schroeder.nosc.mil (Vincent Broman) Newsgroups: comp.sys.apollo Subject: Re: Apollo Pascal Message-ID: Date: 10 May 89 21:37:25 GMT References: <8905022002.AA00179@apollo.bucknell.edu> <20253@iuvax.cs.indiana.edu> <4887@pt.cs.cmu.edu> Sender: nobody@nosc.NOSC.MIL Reply-To: broman@nosc.mil Organization: Naval Ocean Systems Center, San Diego Lines: 24 In-reply-to: jwb@LINDENTHAL.CAE.RI.CMU.EDU's message of 3 May 89 17:22:32 GMT Except for the profiler and debugger, which work for C and Fortran also, Apollo Pascal doesn't come with many tools. The code generated is quite fast, and the facilities available through language extensions and pascal-callable libraries are very extensive. (bit ops, address manipulations, graphics, comms, etc.) The language supported as DOMAIN Pascal has only a superficial resemblance to real Pascal. Don't look for conformance to any standard at all. Even the notion of "type" is changed to use structural equivalence instead of name equivalence of types. The compiler supports separate compilation, of course, but does not provide any type consistency checking at all across files. (none!) You have to arrange that yourself by means of include files, make, etc. Procedure/function arguments to procedures and functions are not allowed. New reserved words are defined. Other fun stuff... Don't bother screaming to Apollo about the atrocities they perpetrate upon a nice language. The responses I've gotten from them are either illiterate or else a variant of "That's not a bug, that's a feature." Vincent Broman, code 632, Naval Ocean Systems Center, San Diego, CA 92152, USA Phone: +1 619 553 1641 Internet: broman@nosc.mil Uucp: sdcsvax!nosc!broman