The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Looking back to 1981 - what pascal was popular on what unix?
Date: Fri, 28 Jan 2022 18:40:36 -0600	[thread overview]
Message-ID: <e680aa97-7a02-5c9c-cf8d-c90243359b7c@gmail.com> (raw)
In-Reply-To: <b9799ec0-e11e-2b88-241c-97c83e220abc@gmail.com>

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

On 1/28/22 5:31 PM, Will Senn wrote:
> On 1/28/22 5:18 PM, Dan Cross wrote:
>> On Fri, Jan 28, 2022 at 6:09 PM Will Senn <will.senn@gmail.com> wrote:
>>
>>     I'm reading in, Kernighan & Plauger's 1981 edition of Software
>>     Tools in Pascal and in the book, the author's mention Bill Joy's
>>     Pascal and Andy Tanenbaum's as being rock solid. So, a few
>>     related questions:
>>
>>     1. What edition of UNIX were they likely to be using?
>>
>>
>> I'm afraid I can't speak to your 2nd and 3rd questions, but I can 
>> offer what I think is a reasonable guess about the first.
>>
>> One of the neat things about Unix and Unix-adjacent books of that era 
>> is that very often the copyright page held some information about the 
>> production of the book itself. I just so happened to have a copy of, 
>> "Software Tools in Pascal" sitting on my desk, and it says, "This 
>> books as set in Times Roman and Courier by the authors, using a 
>> Mergenthaler Linotron 202 phototypesetter driven by a PDP-11/70 
>> running the Unix operating system."
>>
>> Given the PDP-11 and the date (1981) one may reasonably conclude that 
>> it was running 7th Edition. I imagine the pascal was Joy's, from 
>> Berkeley.
>>
>>         - Dan C.
>>
> Great hint. 20 seconds after I hit send on the original email, I came 
> across this:
> http://www.lysator.liu.se/c/bwk-on-pascal.html
>
> Where Brian Kernighan talks about the challenges they faced porting 
> the ratfor examples into pascal. He explains that:
>
>     The programs were first written in that dialect of Pascal
>     supported by the Pascal interpreter pi provided by the University
>     of California at Berkeley. The language is close to the nominal
>     standard of Jensen and Wirth,(6
>     <http://www.lysator.liu.se/c/bwk-on-pascal.html#lit-6>) with good
>     diagnostics and careful run-time checking. Since then, the
>     programs have also been run, unchanged except for new libraries of
>     primitives, on four other systems: an interpreter from the Free
>     University of Amsterdam (hereinafter referred to as VU, for Vrije
>     Universiteit), a VAX version of the Berkeley system (a true
>     compiler), a compiler purveyed by Whitesmiths, Ltd., and UCSD
>     Pascal on a Z80. All but the last of these Pascal systems are
>     written in C.
>
> So, you were right about it being Joy's pi.
>
> Thanks,
>
> Will

On the good news front, I was able to find a working pi/px environment - 
4.2bsd built from tape on simulated vax780 works great (thank god vi 
works there, too) and will run the programs in the book without mods, 
out of the box. 4.3 would probably work similarly (I put it on the 
list). I tried compiling the pascal distributed via 2bsd on v7, but 
wasn't able to get it built (story of my life). This is prolly expected 
because the notes in the distro say "This is still set up for version 
6", so I'll stick with 4.2 for the time being. Just glad to have a 
working environment to supplement the reading.

Will

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

  parent reply	other threads:[~2022-01-29  0: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 [this message]
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
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=e680aa97-7a02-5c9c-cf8d-c90243359b7c@gmail.com \
    --to=will.senn@gmail.com \
    --cc=crossd@gmail.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).