The problem on Win32, is that Win32 dosn't support "select" on pipes. IPC::Open3 uses pipes to connect to the command, while IPC::Run uses sockets( win32 select works on sockets). BUT, if you can figure out a way to NOT use select, and get the pipes flushed, you may be able to use it. Your main problem is output may be sitting in the pipe,
but without $select->can_read, you won't know it. See
Pipe Problem for some ideas.
I don't use MSwindows, but there probably are hacks to get around the problem, like
using sysread to read 1 byte at a time, until nothing is there, or see Non-blocking Reads from Pipe Filehandle
You can use the SuperSearch here for many examples of using Open3, but remember, no select is available to you... so you need a workaround. See Perl/Tk App and Interprocess Communication. If you are using an event-loop system, you can setup a timer to repeatedly read the pipe until no bytes are there. Also see " perldoc -q 'capture STDERR' "
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.