The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Rochkind <mrochkind@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Pipes (was Re: After 50 years, what has the Impact of Unix been?)
Date: Thu, 5 Dec 2024 16:07:14 -0700	[thread overview]
Message-ID: <CAOkr1zUyGNDhy=1hJNsbrboKxZ4MJw79qXb8sv5PHyVepYB3NA@mail.gmail.com> (raw)
In-Reply-To: <002cf6d3-0ed2-46f2-9fae-19a3e10d7b9c@case.edu>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

I found that 2017 paper "Extending Unix Pipelines to DAGs". It's open
access:

https://ieeexplore.ieee.org/document/7903579

The open source code itself is here: https://github.com/dspinellis/dgsh

Maybe an ambitious TUHS contributor can get the code running and give us a
report.

Marc Rochkind

On Thu, Dec 5, 2024 at 3:38 PM Chet Ramey via TUHS <tuhs@tuhs.org> wrote:

> On 12/5/24 5:03 PM, Warner Losh wrote:
>
> > The <() , >()  syntax is a bash extension. Not all shells support it. And
> > I couldn't find them in POSIX Issue 8.
>
> Credit where credit is due: I picked them up from ksh93, and extended
> them to use named pipes on systems where /dev/fd isn't available.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>


-- 
*My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 1894 bytes --]

  reply	other threads:[~2024-12-05 23:07 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 [this message]
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
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='CAOkr1zUyGNDhy=1hJNsbrboKxZ4MJw79qXb8sv5PHyVepYB3NA@mail.gmail.com' \
    --to=mrochkind@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).