If you want to separate the compiler's messages (sent to STDERR) from your own STDERR messages, this will help.

The module is used like so:

use Compiler::Errors 'file.out'; # will append use Compiler::Errors '>file.out'; # will overwrite use Compiler::Errors '>>file.out'; # will append use Compiler::Errors '| program'; # will pipe use Compiler::Errors '>&=1'; # dup to fd
or on the commandline: perl -MCompiler::Errors=file.out -w program
package Compiler::Errors; sub import { shift; # caller my $file = @_ ? shift : "compiler.err"; # default to appending to the file $file = ">> $file" if $file !~ /^[>|]/; open __SAVEERR, ">&STDERR"; # copy STDERR open STDERR, $file; # redirect STDERR } INIT { open STDERR, ">&__SAVEERR"; # restore STDERR close __SAVEERR; } 1;

In reply to Compiler Errors by japhy

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.