Xref: utzoo comp.lang.apl:525 comp.misc:10279 alt.folklore.computers:5698
Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!rpi!bu.edu!shelby!mcnc!mephisto!prism!sun13!sun16.scri.fsu.edu!sandee
From: sandee@sun16.scri.fsu.edu (Daan Sandee)
Newsgroups: comp.lang.apl,comp.misc,alt.folklore.computers
Subject: Re: Pascal Source for APL Interpreter--Want Info
Keywords: Pascal, APL, Byte
Message-ID: <902@sun13.scri.fsu.edu>
Date: 3 Oct 90 16:48:55 GMT
References: <1057@digi.lonestar.org>
Sender: news@sun13.scri.fsu.edu
Followup-To: comp.lang.apl
Organization: SCRI, Florida State University
Lines: 19

In article <1057@digi.lonestar.org> crichmon@digi.lonestar.org (Charles Richmond) writes:
>I have a book entitled _The Byte Book of Pascal_ that was published
>about 12 years ago.  It contains an APL interpreter written entirely
>in Pascal (for the CDC6600, I think).  It is somewhere in the neighbor-
>hood of 50 pages long.  I typed it all into my Atari ST and now cannot
>get it to work.
>
>   Charles Richmond              crichmon@digi.lonestar.org

Well, there's Pascal and Pascal ... and 1970's style CDC Pascal and current
Atari is about as far apart as you can get. Although Pascal is designed as
a machine-independent language, anybody can write a machine-dependent program.
If it was published 12 years ago, it probably indeed was CDC 6000 Pascal.
FYI, the 6000 had 6-bit characters packed 10 to a 60-bit word. Character set
not ASCII but CDC's own. So how about mixing integers and characters through
abuse of chr() and ord()? And packed data types? And records with conditional
clauses of different data type (resulting in different memory allocations)?
And 'set' data type limited to 60 elements? Plenty of opportunity for bad
programming there.