Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re: Windows, threads and IPC::Open3by ikegami (Patriarch) |
on Nov 07, 2010 at 21:01 UTC ( [id://869955]=note: print w/replies, xml ) | Need Help?? |
First of all, that won't work. If either pipes fill up, the child will block and never exit. So let's examine what your original solution doesn't work on Windows:
Using sockets instead of pipes to communicate with the child (as demonstrated here) would solve the first problem, so all that's left would be to use select()'s timeout argument instead of alarm. And now we'll forget everything I said because we don't want to reinvent the wheel. Just use IPC::Run.
In Section
Seekers of Perl Wisdom
|
|