Dear Monks,

I want to capture the output of a program that prints on STDOUT. I could redirect STDOUT to a file like this:

# See the Cookbook p.263 for redirecting standard output. # Copy the STDOUT file descriptors: my $buffer_file = '/path/to/buffer.txt'; open(OLDOUT, ">&STDOUT"); open(STDOUT, "> $buffer_file") or die "Couldn't redirect STDOUT to $bu +ffer_file: $!"; # Call the script whose output I want to capture: do("/path/to/cgi/mhandler.cgi"); # Close the redirected STDOUT and restore the original: close(STDOUT) or die "Couldn't close redirected STDOUT: $!"; open(STDOUT, ">&OLDOUT") or die "Couldn't restore STDOUT: $!"; close(OLDOUT) or die "Couldn't close OLDOUT: $!";

But it would be more useful if I could capture the STDOUT directly into a $buffer variable instead of a file.

Is it possible to open a filehandle into a variable like that?


In reply to Redirecting STDOUT to a variable by Dave05

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.