On Tue, Jun 28, 2011 at 11:03 PM, Dima Kogan <[email protected]> wrote: > Second, if windows supports communication over pipes > then things should just work for the most part. Regarding the "list form of > pipe", the perl open() function can be used to spawn a process directly or > via a > shell: > > open( $handle, '-|', qw(program argument1 argument2) ) runs the process > directly > > open( $handle, '| program argument1 argument2' ) runs the process via a shell > > The direct method is the "list form". Generally doing it directly is > preferable > since it bypasses the extra overhead incurred from the shell. It also removes > the requirement for the shell to split the command string into arguments, > since > this would be done already. The error message seems to imply that the windows > perl requires the shell. Change the script to the second form above and try > again, if you want to experiment. If I understand the error message correctly, > that should make it work.
Yep, that's exactly the problem. See the end of the sixth paragraph in perlopentut at Pipe Opens: http://perldoc.perl.org/perlopentut.html#Pipe-Opens David -- Sent via my carrier pigeon. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
