I have recently started to use a different technique: all the Perl files in my application start with something like:

my %trace=( index_generation => 1,
                  link_computation => 0,
                  link output      => 1,
                );

[download]

and the log statements read like:

print LOG "blah" if( $trace{link_outpout});

When I see a problem in the result (I am doing mostly batch processing here, so YMMV) I can then turn on whatever trace is needed. I find this very convenient, it allows me to focus on whatever area the problem seems to be in.

Of course this could be improved by adding all and none fields to the trace hash, so I could write:

print LOG "blah" if( $trace{all} or ($trace{link_outpout} and !$trace{none}));

Or even better, write a function my_log:

sub my_log
  { my $type= shift;
    print LOG @_ if(    ( $trace{all}
                     or (      $trace{link_outpout}
                          and !$trace{none}
                        )
                   );
  }

[download]

I find this more flexible than just a numeric value, that inevitably ends up filling my log files with garbage. I guess just prefixing the log entry with the type of log and greping it could also work, but I like this way better because I can also use it when I am in debug mode under perl -d.

In reply to Re: Determining debug levels by mirod
in thread Determining debug levels by drewbie

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.