A colleague was creating a process that write to a log file. While debugging his app he wanted to output his log entries to the display rather than his log file. So I came up with this to keep him from re-doing all his print statements.

This is my 1st snippet posting so please be gentle.

$debug = 1; # toggle to 0 to turn off debug
if ($debug) {
    open(FH, ">-") or die "Unable to open STDOUT: $!\n";
} else {
    open(FH, ">/tmp/var/$0$$.log") or die "Unable to open $0$$.log $!\
+n";
}

print FH "If \$debug = 1 this will print to log otherwise print to the
+ screen(STDOUT)\n";

[download]

In reply to Printing "log" output while debugging by sweetblood

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.