Re^2: Child process lingers after keyboard interrupt on Windows

[toughy]

Thank you for the hint on this module.

I believe Proc::Simple does not yet work on Windows. With Strawberry perl, installation from CPAN hangs during 'Building and testing Proc-Simple-1.32', and with ActivePerl from ActiveState the .ppm build failed on all Windows versions: http://code.activestate.com/ppm/Proc-Simple/

I looked at the source on CPAN and what it does is fork() and exec(). I never tried it until now because I found it unintuitive that fork() will work properly on Windows, while IPC::Run will not, but I will try it. I do not like how Proc::Simple will exit(0); after exec() fails, I think that is a silent error and it can be dangerous.

--
Thank you,
Timothy Madden

[toughy]

So trying to fork() I run into the this issue:

When the pseudo-child process (really a new thread in the parent, see perl fork() emulation for Windows) reopens STDOUT, the parent STDOUT changes as well. Although perl documentation says the open handles are duplicated on emulated fork(), to prevent this issue.