The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org, jpl.jpl@gmail.com
Subject: Re: [TUHS] Public access multics
Date: Sun, 02 Sep 2018 17:47:01 -0400	[thread overview]
Message-ID: <201809022147.w82Ll1nu034542@tahoe.cs.Dartmouth.EDU> (raw)

Caveat: As a member of the PL/I committee, and the person who brought
the new and unimplemented language to the attention of Multics, let a
disastrous contract for a compiler, and finally helped cobble together
a rudimentary compiler that got the project off the ground, I am not
exactly an unbiased observer.

A ground tenet of Multics was that it would be programmed in a higher
level language. A subsidiary requirement, which was generally agreed
upon, was language-level access to the logical operators and address
manipulation inherent in the hardware.  No widely used language of the
time met this requirement.  And they didn't want to get sidetracked into
language design.

Discussions finally boiled down to AED, developed at MIT by Doug Ross, and
PL/I. Ross was a brilliant software innovator with a mystical outlook that
made it difficult to distinguish his vision of what could be done from
what actually existed. AED was definitely a moving target. By contrast
PL/I had a written spec, so you knew exactly what could be done in it,
though not how well the compiler would do it.

PL/I  was very big; we deliberately (and explicitly) omitted about
half the spec. The remainder was definitely seen as a "plausible
systems programming language".

From the perspective of the time, why do you think the contrary?

Doug

             reply	other threads:[~2018-09-02 21:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 21:47 Doug McIlroy [this message]
2018-09-03  6:18 ` arnold
  -- strict thread matches above, loose matches on Subject: below --
2018-09-03 13:29 Doug McIlroy
2018-09-03 23:41 ` Dave Horsfall
2018-09-04  2:47   ` Jeffrey H. Johnson
     [not found] <5B48F6A3-374A-4579-AE8F-35BD328D07F9@reagan.com>
2018-09-02  3:17 ` Jeffrey H. Johnson
2018-09-01 23:33 Noel Chiappa
2018-09-01 23:44 ` jcs
2018-09-01 23:25 [TUHS] Fwd: " Noel Chiappa
2018-09-02  4:05 ` Will Senn
2018-09-02  4:25   ` [TUHS] " Jeffrey H. Johnson
2018-09-02 22:30     ` Will Senn
2018-09-01 20:31 Will Senn
2018-09-01 21:27 ` jcs
2018-09-01 23:24   ` John P. Linderman
2018-09-02 13:06     ` Dave Horsfall
2018-09-02 16:23       ` Charles Anthony
2018-09-02 18:18       ` Paul Winalski
2018-09-02 19:09         ` Paul Winalski
2018-09-02  0:57   ` Dan Cross
2018-09-02  2:06     ` Grant Taylor via TUHS
2018-09-02  2:32   ` Charles Anthony
2018-09-02  2:52     ` Larry McVoy

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=201809022147.w82Ll1nu034542@tahoe.cs.Dartmouth.EDU \
    --to=doug@cs.dartmouth.edu \
    --cc=jpl.jpl@gmail.com \
    --cc=tuhs@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).