Thank you.
Stanford PASCAL also generates P-Code in the first step,
which in the second step is translated to 370 machine code.
And: Urs Ammann, who is mentioned in the UCSD article
as the creator of the P-code interpreter, which was the origin
of the UCSD pascal system, is one of the authors of the Pascal P4
compiler, too, which was the origin of the Stanford compiler.
So there must be many similarities, I guess.
BTW: The P-Code of the 1982 variant of the Stanford compiler
had been extended compared to the 1979 variant, and because
I found only a description of the 1979 variant, it was a little bit
complicated
to find out what the "new" P-Code instructions do. There is not "one"
P-Code, but many variants of P-Code.
And: it turned out, that the P-Code is not so machine-independant
as it should be. There will be some difficulties regarding character
sets etc., when I try to port the compiler to an ASCII based platform,
for example (which I would like to do in the future).
Kind regards
Bernd
Am 02.10.2013 01:25, schrieb efinnell15:
http://en.wikipedia.org/wiki/UCSD_Pascal
In a message dated 10/01/13 17:42:33 Central Daylight Time,
[email protected] writes:
I don't know much about UCSD, but AFAIK this is a small PASCAL
implementation
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
