The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] FORTRAN
Date: Wed, 21 Mar 2018 10:51:41 -0400 (EDT)	[thread overview]
Message-ID: <20180321145141.EF02718C088@mercury.lcs.mit.edu> (raw)

    > From: "Steve Johnson"

So, I have this persistent memory that I read, in some early Multics (possibly
CTSS, but ISTR it was Multics) document, a footnote explaining the origin of
the term 'daemon'. I went looking for it, but couldn't find it in a 'quick'
scan.

I did find this, though, which is of some interest: R. A. Freiburghouse, "The
Multics PL/1 Compiler" (available online here:

  http://multicians.org/pl1-raf.html

if anyone is interested).

    > There was a group that was pushing the adoption of PL/1, being used to
    > code Multics, but the compiler was late and not very good and it never
    > really caught on.

So, in that I read:

  The entire compiler and the Multics operating system were written in EPL, a
  large subset of PL/1 ... The EPL compiler was built by a team headed by
  M. D. McIlroy and R. Morris ... Several members of the Multics PL/1 project
  modified the original EPL compiler to improve its object code performance,
  and utilized the knowledge acquired from this experience in the design of
  the Multics PL/1 compiler.

The EPL compiler was written when the _original_ PL/1 compiler (supposedly
being produced by a consulting company, Digitek) blew up. More detail is
available here:

  http://multicians.org/pl1.html

I assume it's the Digitek compiler you were thinking of above?

	Noel


             reply	other threads:[~2018-03-21 14:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 14:51 Noel Chiappa [this message]
2018-03-21 21:57 ` Charles Anthony
     [not found] <mailman.48.1521640130.3788.tuhs@minnie.tuhs.org>
2018-03-21 22:58 ` Johnny Billquist
  -- strict thread matches above, loose matches on Subject: below --
2018-03-19 15:55 [TUHS] RIP John Backus Clem Cole
2018-03-19 16:58 ` [TUHS] FORTRAN Steve Johnson
2018-03-19 17:32   ` Jon Forrest
2018-03-20 17:42     ` Paul Winalski
2018-03-20 17:47       ` George Michaelson
2018-03-19 18:47   ` Larry McVoy
2018-03-20 18:15   ` Dan Cross
2018-03-20 19:55     ` Ron Natalie
2018-03-20 20:21       ` Paul Winalski
2018-03-20 20:27         ` Warner Losh
2018-03-21  8:10         ` Peter Jeremy
2018-03-21 20:56           ` Ron Natalie
2018-03-21 21:15         ` Dennis Boone
2018-03-20 21:36       ` Clem Cole
2018-03-20 21:59         ` Ron Natalie
2018-03-20 23:00         ` Bakul Shah
2018-03-21 13:48         ` Paul Winalski
2018-03-21 20:55           ` Ron Natalie

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=20180321145141.EF02718C088@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).