Isn't IPC::Run3 based on IPC::Run? So if IPC::Run doesn't work...
No, it's smaller, faster, lighter ;)
It's "all new code", no select(). Uses File::Temp temporary files to optionally queue up input for the child, runs the child, optionally with any stdout and/or stderr redirects to other temp files, then slurps the results. Simple. Portable. Relatively efficient for small to moderate amounts of data, especially when you start comparing it to the things that IPC::Run does when faced with the odd behaviors of Win32's anonymous pipe and TCP socket APIs (you want the child to have pipe()s, but you can't select() on pipes, and I don't know how to take a pipe handle that Win32 gives me and do a blocking poll on it a la select()--WaitForMultipleObjects() might do it, but I'm no guru there).
The major non-feature is that you can't have a coprocess; the parent blocks while the child runs.
- Barrie
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
