Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Re: capturing the output of eval()

by damian1301 (Curate)
on May 09, 2001 at 20:21 UTC ( #79150=note: print w/replies, xml ) Need Help??

in reply to capturing the output of eval()

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 STDOUT from the beginning
  • Print it a file. Then open that file and print it to the screen. This is what I hacked up and I am *certain* there is a better way for one of these.

Log from beginning:
BEGIN{ open(STDOUT,">stdout.log")||die"$!"; }

#!/usr/bin/perl use strict; open(LOG,"log.txt") ||die"$!"; select LOG; 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

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://79150]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (5)
As of 2018-06-23 04:54 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (125 votes). Check out past polls.