| [reply] |
I'm amazed that that kind of information is not in the description of the command itself. Anyhow, that being a Win32-specific thing means it's useless for me, as i don't want to lose Linux compatibility.
| [reply] |
Officially, it's an internal call you're suppose to access through modules such as IPC::Open2 and IPC::Open3, both of which are documented and portable.
But yeah, nothing about "1," makes any sense potato.
| [reply] |
How would i know when it's done and what its success was?
Sounds like you want to launch these processes with Win32::Process's Create() function instead of system().
Cheers,
Rob | [reply] |
Good suggestion, certainly a more sensible approach than system, but not really applicable for me. While I want this to be able to run under Win32, i do not want to lose ability to run it under Linux.
| [reply] |
While I want this to be able to run under Win32, i do not want to lose ability to run it under Linux
That might make it more messy. Assuming that the code that works on linux *doesn't* work on windows, you could resort to something like:
if($^O =~ /mswin32/i) {
require Win32::Process;
# do the task using Win32::Process
}
else {
# do the task using whatever it is that works on linux
}
As an alternative, you may find that the code that works on linux also works on windows if run under Cygwin. Is using Cygwin an option ?
Cheers,
Rob | [reply]
[d/l] |