The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Public access multics
Date: Sun, 2 Sep 2018 23:06:19 +1000 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1809022258340.28912@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC0cEp9w=-EVT5jJheEQfgqyKvirkt1pEPo6YNhE1ThC521SRw@mail.gmail.com>

On Sat, 1 Sep 2018, John P. Linderman wrote:

> PL/I was a language designed by a committee, and it showed. [...]

I have never seen a full-blown PL/I compiler (only subsets), and I recall 
being told that there never will be one because it is simply impossible, 
given the spec.

Naturally I am happy to be proven wrong on this.

-- Dave

  reply	other threads:[~2018-09-02 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01 20:31 Will Senn
     [not found] ` <CAC20D2N-Q4VY8TLZagS6J2-US1G3emXVcOdX1BQZ44HYukD6ug@mail.gmail.com>
2018-09-01 20:50   ` [TUHS] Fwd: " Clem Cole
2018-09-01 21:27 ` [TUHS] " jcs
2018-09-01 23:24   ` John P. Linderman
2018-09-02 13:06     ` Dave Horsfall [this message]
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
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 23:33 Noel Chiappa
2018-09-01 23:44 ` jcs
     [not found] <5B48F6A3-374A-4579-AE8F-35BD328D07F9@reagan.com>
2018-09-02  3:17 ` Jeffrey H. Johnson
2018-09-02 21:47 Doug McIlroy
2018-09-03  6:18 ` arnold
2018-09-03 13:29 Doug McIlroy
2018-09-03 23:41 ` Dave Horsfall
2018-09-04  2:47   ` Jeffrey H. Johnson

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.BSF.2.21.9999.1809022258340.28912@aneurin.horsfall.org \
    --to=dave@horsfall.org \
    --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).