From: Larry McVoy <email@example.com>
To: GREEN <firstname.lastname@example.org>
Cc: Bakul Shah <email@example.com>, TUHS main list <firstname.lastname@example.org>
Subject: Re: [TUHS] Looking back to 1981 - what pascal was popular on what unix?
Date: Sat, 29 Jan 2022 19:27:16 -0800 [thread overview]
Message-ID: <20220130032716.GV16452@mcvoy.com> (raw)
So what did you think of Tunis compared to V6?
I really liked the book, I'm hoping it was good but reality is not always that.
On Sat, Jan 29, 2022 at 05:48:39PM -0500, GREEN wrote:
> I was one of the TAs for the grad course that produced Tunis. It was heavily influenced by V6 which we were running at the time. It was designed to run on a stripped down PDP11 so it could be used in a classroom.
> Sent from my iPhone
> > On Jan 29, 2022, at 5:07 PM, Bakul Shah <email@example.com> wrote:
> > ???
> >> On Jan 29, 2022, at 12:34 PM, Larry McVoy <firstname.lastname@example.org> wrote:
> >>> On Sat, Jan 29, 2022 at 12:13:06PM -0800, Bakul Shah wrote:
> >>> On Jan 29, 2022, at 11:59 AM, Clem Cole <email@example.com <mailto:firstname.lastname@example.org>> wrote:
> >>>> Plus, the "Tunis" folks in Toronto had a Concurrent-Pascal and a UNIX-like system that ran on PDP-11s.
> >>> Tunis was implemented in Concurrent Euclid, a descendant of
> >>> the Euclid programming language, designed by Ric Hort and
> >>> James Cordy.
> >> I read the Tunis book, it seemed pretty cool from the book but I've never
> >> played with it. Has anyone?
> > From Tunis I borrowed signal() & wait() as synchronization
> > primitives for the simulation library I wrote in 1983 but
> > that was about it.
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2022-01-30 4:41 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 [this message]
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
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).