Why not make Log::Log4perl a Prerequisite for your module? That way, your users can decide whether or not they want to see the log messages...

I've decided on needing Log::Log4perl with WWW::Mechanize::Chrome instead of writing another logging implementation myself, to give others the chance of reusing and integrating it.

The downside I've found is that now every script and test script also has to initialize Log::Log4perl or a warning will be issued. But that's just two lines of configuration:

use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init($ERROR);

[download]

And whenever I need more information, I have to change $ERROR to $TRACE (or maybe $DEBUG).

In reply to Re: Leave log4perl debug code in cpan module? by Corion
in thread Leave log4perl debug code in cpan module? by nysus

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.