in reply to Re: Forking children operate sequentially?!
in thread Forking children operate sequentially?!

Thanks ikegami.

Is it possible to *not* wait for the child to return output, yet still capture it?

Yeah, those names suck. I copied it from some other code, I think it originated from the cookbook.

  • Comment on Re^2: Forking children operate sequentially?!

Replies are listed 'Best First'.
Re^3: Forking children operate sequentially?!
by ikegami (Patriarch) on Mar 11, 2010 at 20:23 UTC

    Is it possible to *not* wait for the child to return output, yet still capture it?

    Well, what you want to do is move the waiting to the outside of the loop, and wait for all the children "at once" (via polling, select, or whatever). Below is a solution using Thread::Queue.