To get the output of STDERR, eval comes along with a neat variable that captures the errors during the evaluation process.

To capture STDOUT, you have two options:
Log from beginning:
BEGIN{ open(STDOUT,">stdout.log")||die"$!"; }

#2
#!/usr/bin/perl use strict; open(LOG,"log.txt") ||die"$!"; select LOG; #...do stuff here close LOG; select STDOUT; # I love ar0n :) my $thing = do { local @ARGV = "foo.txt"; <> }; print $thing;
That way you get the stuff printed to the file and to STDOUT. I am sure there is a better way to do it. Monks, enlighten me(us). :)
UPDATE: I just noticed I really messed up on the question. Forgive me.

Tiptoeing up to a Perl hacker.
Dave AKA damian


In reply to Re: capturing the output of eval() by damian1301
in thread capturing the output of eval() by tmbg

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.