The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Alexis <flexibeast@gmail.com>
To: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Pipes (was Re: After 50 years, what has the Impact of Unix been?)
Date: Fri, 06 Dec 2024 11:46:43 +1100	[thread overview]
Message-ID: <87ttbhzlho.fsf@gmail.com> (raw)
In-Reply-To: <002cf6d3-0ed2-46f2-9fae-19a3e10d7b9c@case.edu> (Chet Ramey via TUHS's message of "Thu, 5 Dec 2024 14:19:43 -0800")

Chet Ramey via TUHS <tuhs@tuhs.org> writes:

> 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.

i must say i was moderately surprised to learn a few years ago 
that process substitution wasn't in POSIX - i find it succinct 
syntactic sugar. There's a post on Chris Siebenmann's blog about 
some of the issues involved, including the /dev/fd issue:

  https://utcc.utoronto.ca/~cks/space/blog/unix/ProcessSubstitutionWhyLate

Can anyone point me to any discussions about process substitution 
potentially becoming part of POSIX? This search on the Austin 
Group tracker didn't yield any useful results:

https://austingroupbugs.net/search.php?project_id=0&search=process+substitution&sticky_issues=off&sortby=last_updated&dir=DESC&hide_status_id=-2&FILTER_SEARCH_PLATFORM=


Alexis.

  parent reply	other threads:[~2024-12-06  0:46 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 [this message]
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=87ttbhzlho.fsf@gmail.com \
    --to=flexibeast@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).