Jonathan Nieder dixit:
>A common use of <(...) is to parse output from a command and let it
>influence the current environment:
>
> while read key value
We use coprocesses for that.
>The "producer" command here could produce a potentially infinite
>stream of output.
I think this case is best be met with a coprocess then.
>The application that led me to mention process substitution to you
>also involved concurrent processes.
>
> producer |
> tee >(xz >log.xz) |
> consumer
True, there’s >(…) which I hadn’t thought of. So the complex
fd/pipe logic must still be there. GNU bash doesn’t mention
=(…) though so I guess we should take this to a cross-shell-
developers discussion instead.
(Are you ok with closing the Debian BTS part of this? If you
want, I can move it to Launchpad, if you’d prefer to have it
not just on a mailing list.)
bye,
//mirabilos
--
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward Burr
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
