An alternative is to avoid the tmpfile altogether and tie an IO::Scalar for capturing the output. We can also localize STDOUT and STDERR (rather than select) and provide a simple __WARN__ sig handler to make up for some of the mentioned caveats: 

    #!/usr/bin/perl -w
    use strict;
    use IO::Scalar;
    use Carp;

    my $out = eval_print_trap(<<'EOC');
        print "Hello World\n";
        print STDOUT "Hello again\n";
        print STDERR "stderr is here too\n";
        print "this uninit warning is captured:$a\n";
        warn "and explicit warnings as well";
        system(q|echo "Can't have everything!"|);
    EOC

    print "***\n$out***\n";
    print "done\n";

    sub eval_print_trap {
        my $code = shift;

        my $string;
        my $SH  = IO::Scalar->new_tie(\$string);

        {
            local *STDOUT = $SH;
            local *STDERR = $SH;
            local $SIG{__WARN__} = sub{print @_};
            eval($code);
        }

        if($@){
            confess "Evaling\n'$code'\ngave error $@";
        }
        return $string;
    }
    __END__
    ### could also have this at the end:
    seek($SH,0,0);
    wantarray ? <$SH> : $string;

[download]

In reply to Re: Re (tilly) 1: codeopen(INPUT, "&lt;INPUT") gives INPUT opened only for output by danger
in thread codeopen(INPUT, "&lt;INPUT") gives INPUT opened only for output by belg4mit

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.