Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sm.unisys.com!csun!csuna!abcscnuk
From: abcscnuk@csuna.UUCP (Naoto Kimura)
Newsgroups: comp.lang.pascal
Subject: Re: Parsing the command line ...
Message-ID: <1661@csuna.UUCP>
Date: 10 Feb 89 21:47:40 GMT
References: <547@loligo.cc.fsu.edu> <1656@csuna.UUCP> <551@loligo.cc.fsu.edu>
Reply-To: abcscnuk@csuna.UUCP (Naoto Kimura)
Distribution: na
Organization: California State University, Northridge
Lines: 22

In article <551@loligo.cc.fsu.edu> perrone@loligo.UUCP (Perrone Ford) writes:
]	Did I hear you correctly?  You have a cyber? what cyber might 
]that be and what pascal are you running on it.  Also thanks for
]the great info on the comand line parsing or reading,,,
]
]Perrone Ford

We've got a Cyber 170/750 running NOS (2.3).  The version of pascal we
use is PASCAL-6000 (V4.1.E), and on the compiler listing we get "E.T.H.
ZEURICH / UNIVERSITY OF MINNESOTA".  I pretty much trust the compiler,
as this compiler is a descendant of the original pascal compiler written
for the CDC 6600.  Using the Cyber made me appreciate the EOF() and
EOLN() functions of pascal (newline is defined to be 12 zero bits
aligned on a word boundary -- which meant you had to be careful in
outputting colons -- unless you were working with the 6/12 character
set).

                //-n-\\				Naoto Kimura
        _____---=======---_____			(csun!csuna!abcscnuk)
    ====____\   /.. ..\   /____====
  //         ---\__O__/---         \\	Enterprise... Surrender or we'll
  \_\                             /_/	send back your *&^$% tribbles !!