From: WEB <hveit01@web.de>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
Date: Mon, 31 Jan 2022 08:59:06 +0100 [thread overview]
Message-ID: <864d655d-35e3-a805-b187-b52aae6dba7d@web.de> (raw)
In-Reply-To: <075FBF35-8327-4BD1-B532-C7D7DC71375A@kdbarto.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Am 30.01.2022 um 21:09 schrieb David Barto:
>
>> On Jan 30, 2022, at 10:08 AM, Dan Stromberg <drsalists@gmail.com> wrote:
>> On Sun, Jan 30, 2022 at 8:58 AM David Barto <david@kdbarto.org> wrote:
>>
>> Yes, the UCSD P-code interpreter was ported to 4.1 BSD on the VAX
>> and it ran natively there. I used it on sdcsvax in my senior year
>> (1980).
>>
>>
>> This reminds me of a question I've had percolating in the back of my
>> mind.
>>
>> Was USCD Pascal "compiled" or "interpreted" or both?
[..]
> UCSD Pascal was “compiled” into the byte code of the interpreter. I
> wrote a P-code assembler in my senior year as part of the compiler
> class. Java started out doing the same thing and over time native code
> generation was added in gcj.
Just for the record: There has been the WD9000 chipset which is actually
an LSI-11 with different Microms which could run the P-code (of UCSD
Pascal III) natively as it was its machine code. So this makes a
distinction of interpreted vs compiled even more fuzzy.
Holger
[-- Attachment #2: Type: text/html, Size: 2599 bytes --]
next prev parent reply other threads:[~2022-01-31 8:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 23:07 [TUHS] " Will Senn
2022-01-28 23:18 ` Dan Cross
2022-01-28 23:31 ` Will Senn
2022-01-29 0:03 ` Rob Pike
2022-01-29 0:40 ` Will Senn
2022-01-29 19:05 ` John Cowan
2022-01-29 19:36 ` arnold
2022-01-29 19:59 ` Clem Cole
2022-01-29 20:02 ` Jon Steinhart
2022-01-29 20:13 ` Bakul Shah
2022-01-29 20:30 ` Clem Cole
2022-01-29 20:34 ` Larry McVoy
2022-01-29 21:03 ` Al Kossow
2022-01-29 21:38 ` Larry McVoy
2022-01-29 22:06 ` Bakul Shah
2022-01-29 22:48 ` GREEN
2022-01-30 3:27 ` Larry McVoy
2022-01-30 16:57 ` David Barto
2022-01-30 18:07 ` [TUHS] Compilation "vs" byte-code interpretation, was " Dan Stromberg
2022-01-30 20:09 ` David Barto
2022-01-31 7:59 ` WEB [this message]
2022-01-30 22:51 ` Dan Cross
2022-01-30 23:57 ` Dan Stromberg
2022-01-31 0:23 ` Nemo Nusquam
2022-01-31 0:45 ` Steve Nickolas
2022-01-31 17:16 ` Paul Winalski
2022-01-31 20:00 ` Erik E. Fair
2022-01-31 22:45 ` Steve Nickolas
2022-02-02 4:53 ` Adam Thornton
2022-01-31 1:41 ` Phil Budne
2022-02-07 3:04 ` [TUHS] " Rob Gingell
[not found] <A84C7761-A80D-4F8D-B541-2C7F7E5B5E39@hotmail.co.uk>
2022-01-30 20:09 ` [TUHS] Compilation "vs" byte-code interpretation, was " silas poulson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864d655d-35e3-a805-b187-b52aae6dba7d@web.de \
--to=hveit01@web.de \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).