Check out

my $stdout_and_stderr1; my $stdout_and_stderr2; my $stdout_and_stderr3; { print "running script1.pl\n"; local *STDOUT; close(STDOUT); open(STDOUT, '>', \$stdout_and_stderr1) or die("..."); local *STDERR; close(STDERR); open(STDERR, '>&STDOUT') or die("..."); do 'script1.pl'; } { print "running script2.pl\n"; ...

The above requires 5.8(.0? .1?). IO::Scalar can be used with older versions of Perl, but it has limitations.

If you don't mind running the script in a seperate process, I think this works:

$stdout_and_stderr1 = `script1.pl 2>&1`; $stdout_and_stderr2 = `script2.pl 2>&1`; $stdout_and_stderr3 = `script3.pl 2>&1`;

Untested


In reply to Re: STDOUT and STDIN question by ikegami
in thread STDOUT and STDIN question by Anonymous Monk

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.