The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: David Barto <david@kdbarto.org>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Looking back to 1981 - what pascal was popular on what unix?
Date: Sun, 30 Jan 2022 08:57:20 -0800	[thread overview]
Message-ID: <9E47A62E-3AAD-491E-9164-3DCAD22EC1F7@kdbarto.org> (raw)
In-Reply-To: <CAC20D2Nh0t9dxVbRvXFxXkCfEaWkmp9MP1Xf+=YC3rfXf3SK3g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]



> On Jan 29, 2022, at 11:59 AM, Clem Cole <clemc@ccc.com> wrote:
> 
> 
> 
> On Fri, Jan 28, 2022 at 6:08 PM Will Senn <will.senn@gmail.com <mailto:will.senn@gmail.com>> wrote:
> 
> 3. What combinations of UNIX/Pascal were popular?
> Depends the implementation...  there were a number of them... there were the ones I had at that time
> The Zurich P4 compiler was around and of course eventually begat UCSD, but I don't remember that it was directly made to run on Unix[I did not have one], although it may/must have been.
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).

	David


[-- Attachment #2: Type: text/html, Size: 2357 bytes --]

  parent reply	other threads:[~2022-01-30 16:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 23:07 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 [this message]
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
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

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=9E47A62E-3AAD-491E-9164-3DCAD22EC1F7@kdbarto.org \
    --to=david@kdbarto.org \
    --cc=clemc@ccc.com \
    --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).