|Keep It Simple, Stupid|
Re^8: Is there a problem with IPC::Open on Windows 7?by BrowserUk (Pope)
|on Aug 13, 2013 at 16:18 UTC||Need Help??|
Here is one implementation which I based mine: https://github.com/lucastheisen/ipc-open3-callback
Okay. That makes more sense than your original description -- though I see how you arrived at that description.
Essentially, they are doing the same thing as Win32::SocketPairopen2() and Win32::SocketPairopen2_5() (original author:salva), in that they are redirecting the outputs from the commands via socket pairs, which are selectable.
I'm like the idea of IPC::Open3::Callback. It is a very clever way to address both the problems with IPC::Open3.
However, as it stands, it steals both the pid of the subprocess, and the stdin; which make it less useful than it could be. I can see myself stealing the idea of the callbacks and producing my own version that corrects for those. (Assuming the author doesn't modify his interface before sending it to cpan :)
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.