Sujet : coprocs in bash & ksh (Was: Different variable assignments)
De : gazelle (at) *nospam* shell.xmission.com (Kenny McCormack)
Groupes : comp.unix.shellDate : 19. Oct 2024, 14:39:14
Autres entêtes
Organisation : The official candy of the new Millennium
Message-ID : <vf0cq2$3djd7$2@news.xmission.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
vf08fi$3sf5e$1@dont-email.me>,
Janis Papanagnou <janis_papanagnou+
ng@hotmail.com> wrote:
...
Please note that while ksh supports co-processes it doesn't use (to my
knowledge) the keyword 'coproc'. - Kornshells co-processes are invoked
by appending the '|&' token to a command and reads and writes are done
with 'read -p' and 'print -p', respectively.
Seems to be pretty much the same thing, but with a slightly different
notation (|& vs. "coproc"). I think the original bash designers wanted to
be at least sort of "csh compatible", so they took |& from csh to mean
"merge stdout and stderr", so had to come up with something else for
coprocs.
Anyway, all I know about ksh is basically what I've read from various bash
sources.
-- "We are in the beginning of a mass extinction, and all you can talkabout is money and fairy tales of eternal economic growth." - Greta Thunberg -