With Perl's in-memory filehandles I get "run3(): Bad file descriptor redirecting STDIN at ...". With IPC::Run and, again, with Perl's in-memory filehandles, script just dies without giving any reason "at C:/PDL24/perl/vendor/lib/IPC/Run.pm line 1852." With references to scalars, IPC::Run works, it seems, just like IPC::Run3.

The IPC::Run documentation is a bit overwhelming, I'll browse through it, at leisure :)

As to "premature optimization" - of course, the solution with IPC::Run3 and temp files will work fine. It's not that something is broken and I'm desperate and asking someone to do a research for me. I just thought maybe there already is (and has been for a long time) some FAQ list with nicely enumerated items, etc. :) Thank you for answer.


In reply to Re^2: When does IPC::Open\d work on Windows, and when doesn't? by vr
in thread When does IPC::Open\d work on Windows, and when doesn't? by vr

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.