The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: After 50 years, what has the Impact of Unix been?
Date: Thu, 5 Dec 2024 20:36:15 -0500	[thread overview]
Message-ID: <CAKH6PiUfZwHdxTUYUG1wi_gXfLt9XX1U=CeiM1Xe8b9xH=WuoA@mail.gmail.com> (raw)

> Pipes were invented at least three times

I would add a 4th: POGOL--a remarkable data-processing language from
NSA, described by Gloria Lambert at the first POPL conference, 1973. A
POGOL program is made of processes that read and write notional files.
The compiler considers all the processes together and optimizes files
out of existence wherever it sees that written data can be read
immediately. Otherwise a buffering file is instantiated. Unlike Unix
pipes, though, a pair of communicating processes must share common
knowledge about the connection--the file name.

A ready-made theory of pipe networks was published essentially
simultaneously with the advent of DTSS communication files:
R.M. Karp, R.E. Miller, and S. Winograd. The organization of
computations for uniform recurrence equations. Journal of the ACM,
14(3):563-590, July 1967.

Completely unsuspecting processes could have been connected by a pair
of DTSS communication files controlled by a master relay process. As
far as I know this was never done, although such a mechanism was used
for the DTSS chat facility.

For the special case of clocked sample-data networks, BLODI (block
diagram compiler) by Lochbaum, Kelly and Vyssotsky was way ahead
(1960) of all the pipe-based formalisms.

Doug

             reply	other threads:[~2024-12-06  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  1:36 Douglas McIlroy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-04 19:07 Douglas McIlroy
2024-12-04  3:17 [TUHS] " sjenkin
2024-12-04 13:05 ` [TUHS] " Marc Donner
2024-12-04 13:40   ` William Cheswick
2024-12-04 15:02   ` Rich Salz
2024-12-05  3:08   ` John Levine

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='CAKH6PiUfZwHdxTUYUG1wi_gXfLt9XX1U=CeiM1Xe8b9xH=WuoA@mail.gmail.com' \
    --to=douglas.mcilroy@dartmouth.edu \
    --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).