The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dot@dotat.at (Tony Finch)
Subject: [TUHS] Unix stories, Stephen Bourne and IF-FI in C code
Date: Tue, 10 Jan 2017 12:24:58 +0000	[thread overview]
Message-ID: <alpine.DEB.2.11.1701101208390.7102@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <7e8fd8694d992170208e854db5dd0f72c552016b@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]

Steve Johnson <scj at yaccman.com> wrote:

> I can certainly confirm that Steve Bourne not only knew Algol 68, he
> was quite an evangelist for it.  When he came to the labs, he got a
> number of people, including me, to plough through the Algol 68 report,
> probably the worst written introduction to anything Ive ever read. 

This is a bit off topic, sorry, but a couple more Algol 68 observations...

> They were firmly convinced they were breaking new ground and
> consequently invented new terms for all kinds of otherwise familiar
> ideas.  It was as if the report had been written in Esperanto...  

Or maybe Latin with the way it inflects words e.g. the -ETY suffix being
sort for "or empty", i.e. an optional thing. Though I don't know what
would be a good comparison for all the elision, e.g. MOID = MODE or VOID,
MODINE = MODE or ROUTINE. (a MODE is what they call a type...)

There's a nicely te-typeset version at
http://www.eah-jena.de/~kleine/history/languages/Algol68-RevisedReport.pdf

The other classic of Algol 68 literature was the Informal Introduction, in
which the structure of the book was arranged in two orthogonal dimensions.
The table of contents is a sight to behold.

http://www.softwarepreservation.org/projects/ALGOL/book/Lindsey_van_der_Meulen-IItA68-Revised-ContentsOnly.pdf

One of my ex-colleagues (now retired) was Chris Cheney, who worked with
Steve Bourne on the Algol 68C project. I think it was on that project
where he invented his beautiful compacting copying garbage collector
algorithm.

Tony.
-- 
f.anthony.n.finch  <dot at dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Trafalgar: North 5 to 7, occasionally 4 at first. Slight or moderate, becoming
rough or very rough except in far southeast. Occasional rain. Moderate or
good.


  reply	other threads:[~2017-01-10 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  2:30 Norman Wilson
2017-01-09  3:31 ` Steve Johnson
2017-01-09 15:30   ` Marc Rochkind
2017-01-09 15:45     ` arnold
2017-01-09 15:59       ` ron minnich
2017-01-09 16:03       ` Clem Cole
2017-01-10 18:44         ` Lawrence Stewart
2017-01-09 18:48     ` Derek Fawcus
2017-01-09 20:35     ` Steve Johnson
2017-01-10 12:24       ` Tony Finch [this message]
2017-01-11  6:00   ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2017-01-10 13:50 Noel Chiappa
2017-01-10  4:40 Rudi Blom
     [not found] <mailman.1.1484013601.5032.tuhs@minnie.tuhs.org>
2017-01-10  3:11 ` Paul McJones
2017-01-09  1:06 Doug McIlroy
2017-01-09  2:18 ` Random832
2017-01-08 20:37 Walter F.J. Mueller
2017-01-08 21:12 ` Larry McVoy
2017-01-08 21:26   ` Dave Horsfall
2017-01-08 21:54 ` Kay Parker   
2017-01-08 23:14 ` Adam Sampson

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=alpine.DEB.2.11.1701101208390.7102@grey.csi.cam.ac.uk \
    --to=dot@dotat.at \
    /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).