| [reply]
[d/l] |
I don't have Windows, and besides, that would completely defeat the purpose: I don't want to have to think about platform issues or any error-handling beyond trapping exceptions. I want a module that does all that for me. I like IPC::System::Simple, for example, which appears to do a nice job of it if all I want to do is system or backticks. IPC::Run may or may not succeed in doing it for interactive IPC, I'm still trying to figure that out.
| [reply]
[d/l] |
Sorry, for trying to help.
My experiences of using IPC::Run on windows are dire. It is an over-engineered behemoth of a module that attempts to use *nix techniques to provide *nix capabilities on Windows, and fails dismally.
The point about winopen2 is that it provides you with a pair of selectable handles connected to the child process' STDIN & STDOUT.
As such, it is 'compatibile' with *nix-style code written using IPC::Open2 and select.
Ie. you'd only need do something like:
my( $in, $out );
if( $^O eq 'MSWin32' ) {
($in, $out ) = winopen2( $theCommand );
}
else {
open2( $in, $out, $theCommand );
}
...
select .....
But, its not in a module so ...
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".
| [reply]
[d/l] |
It seems to me that your response of
besides, that would completely defeat the purpose: I don't want to have to think about platform issues
conflicts with
I started implementing the module I have been imagining,
that was stated in the node that was being responded to.
At least, I expect that creating a module that saves users from having to deal with "platform issues" that they would otherwise have to deal with pretty much requires that the author "think about [those] platform issues".
| [reply] |
