The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah via TUHS <tuhs@tuhs.org>
To: Dan Cross <crossd@gmail.com>
Cc: johnl@taugh.com, tuhs@tuhs.org, marc.donner@gmail.com
Subject: [TUHS] Re: Pipes (was Re: After 50 years, what has the Impact of Unix been?)
Date: Thu, 5 Dec 2024 14:05:26 -0800	[thread overview]
Message-ID: <19B4DBDC-4342-4557-925D-8D546DC9D84F@iitbombay.org> (raw)
In-Reply-To: <CAEoi9W4WAb9JO8VAPpHH9eB0=-EnJr0MySt_YH_eTUdTERqoUw@mail.gmail.com>

On Dec 5, 2024, at 1:13 PM, Dan Cross <crossd@gmail.com> wrote:
> 
> And indeed these things are pretty nifty, but don't they generate
> trees, and not arbitrary dags? They don't quite capture the full
> generality of Morrison-style networks since it doesn't seem like
> there's a way to connect process substitution fan-out with fan-in; at
> least, not conveniently.

Isn’t that a limitation of the shell language(s)? It would be
easier in a 2D graphical shell but that would perhaps make
specifying the more common simpler pipelines harder!

A "linear" syntax would require *naming*. For example,

let-proc a = "foo -a", b = "bar -c -d", c = "zee" in
  a.in1 = file1, a.in2 = file2, b.in1 = a.out, b.in2 = file3,
  c.in1 = b.out1, c.in2 = a.out, c.out = file4;

Here names a, b & c are used to denote *processes*, with
connections specified in the next two lines. Once all the
pipes are created, processes a, b & c can be started giving
them the right endpoints in forked processes prior to execing.
Doable but not really worth it. At this point you may as well
use s-expressions!

  parent reply	other threads:[~2024-12-05 22:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  3:17 [TUHS] After 50 years, what has the Impact of Unix been? 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
2024-12-05 15:19     ` [TUHS] Re: Pipes (was Re: After 50 years, what has the Impact of Unix been?) Dan Cross
2024-12-05 16:00       ` John R Levine
2024-12-05 16:17         ` Heinz Lycklama
2024-12-05 17:06           ` Marc Rochkind
2024-12-05 17:53             ` John Cowan
2024-12-05 18:05             ` John Levine
2024-12-05 17:22           ` Paul Winalski
2024-12-05 18:19         ` Ron Natalie
2024-12-06  2:29           ` Adam Thornton
2024-12-07 20:38             ` Ron Natalie
2024-12-05 16:55       ` Adam Thornton
2024-12-05 17:35       ` Chet Ramey via TUHS
2024-12-05 20:55         ` arnold
2024-12-05 21:12           ` Dan Cross
2024-12-05 21:50             ` Marc Rochkind
2024-12-05 22:03             ` Warner Losh
2024-12-05 22:19               ` Chet Ramey via TUHS
2024-12-05 23:07                 ` Marc Rochkind
2024-12-06  8:16                   ` Diomidis Spinellis
2024-12-06  0:46                 ` Alexis
2024-12-06 21:46                   ` Chet Ramey via TUHS
2024-12-05 23:07               ` arnold
2024-12-06  1:09                 ` G. Branden Robinson
2024-12-06  1:31                   ` Greg A. Woods
2024-12-06  2:05                     ` Steve Nickolas
2024-12-06 16:44                     ` arnold
2024-12-05 22:05             ` Bakul Shah via TUHS [this message]
2024-12-06  2:02             ` John Levine
2024-12-06  2:21               ` Dan Cross
2024-12-06 16:46                 ` arnold
2024-12-06  2:26 Douglas McIlroy

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=19B4DBDC-4342-4557-925D-8D546DC9D84F@iitbombay.org \
    --to=tuhs@tuhs.org \
    --cc=bakul@iitbombay.org \
    --cc=crossd@gmail.com \
    --cc=johnl@taugh.com \
    --cc=marc.donner@gmail.com \
    /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).