You can do away with the FIFO entirely using IO::Scalar. Hope this helps. :) tie *OUT, 'IO::Scalar', \$foo

Then select this filehandle in whatever code needs to have its output captured.

By the way, this question's somewhat misnamed -- when it comes down to it, you want to get some output into a variable; the FIFO problems are just an artifact of the particular approach that you're taking. Despite this, you only devote the first and last sentences to your real goal.

In general, you'll get more useful responses if you say "I want to do X! (Y is what came to mind, but it doesn't work quite right)" rather than "I'm doing Y! (p.s. it's because I want X)". X is desired, Y is nonessential, so focus on X, not Y. I hope that makes sense. :)

hdp.

In reply to Re: FIFO buffer size limits by hdp
in thread FIFO buffer size limits by kostya

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.