Since I can't easily tell the two apart from the command prompt, I don't really how to be sure if anything I put in has worked.
Tell apart STDOUT and STDERR? Just redirect them to separate files: 
perl yourscript.pl >stdout.txt 2>stderr.txt

[download]

Although I feel local'izing the file handles is cleaner, as suggested by JavaFan, you could alternatively store them. Then re-store them. That way, you'd have STDERR available in the block if you needed it. 

my ($out, $err) = (*STDOUT, *STDERR);
eval{
    *STDERR = *STDOUT;

    # pod2html code here
    # ...
};
*STDOUT = $out; *STDERR = $err;

[download]

In reply to Re: Tidying up after redirecting STDERR by crashtest
in thread Tidying up after redirecting STDERR by davies

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.