Re: Multiple concurrent coprocesses

[Zachary Santer]

Okay. I've at least seen job control report when each coprocess I created
on the command line has ended, instead of waiting until they're all dead.
And the coproc name going through name expansion is nice. Unless and until
I'm allowed to bring my script home, I won't be able to show off what it's
able to do, taking advantage of this Bash installation, though.

I'm curious what satisfactory testing would look like.

Zack

On Sat, Mar 20, 2021 at 12:25 PM Chet Ramey <chet.ramey@case.edu> wrote:

> On 3/20/21 11:47 AM, Zachary Santer wrote:
> > Multiple concurrent coprocesses simplified one of my scripts a good bit,
> > and then I ran into this
> > <https://lists.gnu.org/archive/html/bug-bash/2011-04/msg00056.html>.
> > Considering a decade has passed, I'm assuming the ship has kind of sailed
> > on Chet finishing support for it, so I'm curious what's missing. I might
> > like to submit my own patch.
>
> It's been there for years; it's just not enabled by default. You have to
> build bash with MULTIPLE_COPROCS=1.
>
> Try it with bash-5.1 and let me know. The reason it's not enabled by
> default is I haven't been able to test it to a level that satisfies me.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>