Part 1:

I'm guessing it's executing join(' ', @command) and the child perl parses it, or the joined string is passed to cmd /c which parses it.

Part 2:

1) I like this tying approach. However, I heard tie was really slow compared to a class that do the same thing. You might want to write and use a subclass of IO::Handle instead of tying.

2) Try not using > inside of <>: <$$self{handle}>.

3) gensym works great: (tested)

use IO::Handle; # for gensym
my $handle = gensym;
tie *$handle, 'call_waitpid', $rdrfh, $pid;
return $handle;

[download]

In reply to Re: IPC::Open3 and Win32 by ikegami
in thread IPC::Open3 and Win32 by moseley

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.