Re: Subjective "valuations" are all we have (Was: coprocs - again (Was: Different variable assignments))

In article <vffoij$349j2$1@dont-email.me>,
Janis Papanagnou  <janis_papanagnou+ng@hotmail.com> wrote:
...

This post should also explain why I think that your valuation that
in Ksh the feature "just grew" is not justified. Beyond the '|&' vs.
'coproc' reserved word; consistency with '|' and '&', redirection,
assigned FDs (if desired), consistent 'p' as read/print option and
as FD, all fits and allows for readable straightforward code in Ksh
that also doesn't leave me with questions.

I have no further comment on the issues you seem to have with the bash
implementation of coprocs.  I think I've explained everything (more than
once) already in these threads.

BTW, co-processes were designed into the shell with Ksh88 already;
not much to "just grow" (as you insinuated). ;-)

Don't be afraid.  Sometimes people are attracted to "just grew".  They like
and admire that organic look.  I really do think that ksh's implementation
of coprocs has an "organic" look.  As I said, bash's way seems much more
"designed".

P.S.  To answer one question, "coproc" *is* a shell keyword in bash:

 $ type coproc
 coproc is a shell keyword
 $

I think you will find that |& is also a keyword (in ksh), although I could
not get "type" (or anything similar) to confirm that suspicion.

--
There's nothing more American than demanding to carry an AR-15 to
"protect yourself" but refusing to wear a mask to protect everyone else.