This is not quite the question I thought of in the chatterbox. Use the IO::Scalar module from CPAN. 
use IO::Scalar;
my $capture;
tie(*CAPTURE, 'IO::Scalar', \$capture);
select (CAPTURE);

[download]
And now the output goes into $capture. For details I suggest reading up on tie.

BUT this approach has a big gotcha. Any and all output that comes from Perl will be captured. Any and all output that is done in C is unlikely to be. So for instance any print you do goes to $capture. But if you make a system call, not a chance.

The safer approach is to run a second process like this: 

local *CAPTURE;
my $cmd = join " ", "perl", "script_name", @args);
open (CAPTURE,  "$cmd |") or die "Cannot run command $cmd: $!";

[download]
And now the STDOUT of the second process can be read and processed by the first. (On Unix you could actually do a fork and have one process read from the other - the Cookbook has an example.)

EDIT
If people are actually reading this I would like to point out a minor detail. Note how I put the command to run into a variable? I make it a point to always do that so that I don't have to synchronize code to get the debugging message to correctly report what failed. Even if it means having a line like: 

my $file = "foo.txt";

[download]
A small but significant detail I like to pay attention to. :-)

In reply to Re: monitor STDOUT in scalar by tilly
in thread monitor STDOUT in scalar by eak

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.