Re: Different variable assignments

In article <vf1942$1uso$1@dont-email.me>,
Lawrence D'Oliveiro  <ldo@nz.invalid> wrote:

On Sat, 19 Oct 2024 14:52:01 +0200, Janis Papanagnou wrote:
>

Also, if above code is how to use co-processes in Bash, I consider that
extremely clumsy (if compared to, say, Ksh).

"extremely" seems more than a bit over the top.  Maybe somewhat clumsy, but
hardly "extremely".

Bash allows for named coprocs. That means you can have multiple coprocs
going at once.

Yes, but only if you re-compile your own version of bash, with that option
turned on in one of the config.h files.

To be precise, multiple co-procs will seem to work even if not enabled as
described above, but things then start to go awry in mysterious ways.  I've
experienced exactly this until I did the research into how to properly
enable it.

But, yes, that's part of the point of making it possible to assign a name
to a coproc (instead of just taking the default of "coproc").

--
If Jeb is  Charlie Brown kicking a football-pulled-away, Mitt  is a '50s
housewife with a  black eye who insists to her  friends the roast wasn't
dry.