No harder than your method, since you can pass open file handles to open3 or open-style dup instructions.

STDIN is moot. None of solutions pass anything to STDIN, since we weren't asked to pass anything to STDIN. You can close the child's STDIN if you want, or you can tie it to the parent's STDIN (by passing '<&STDIN') if you want.

Similarly, you can do anything you want with the child's STDOUT. You can tie it to the parent's STDOUT ('>&STDOUT'), you can close it, you can redirect it to /dev/null, etc.

In reply to Re^6: Capturing STDERR using IO::Handle by ikegami
in thread Capturing STDERR using IO::Handle by rvosa

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.