One slick way to handle that is by localizing STDERR. If $LOG is a reference to a file handle to log to, 

use Module1 qw/$LOG/;
use Module2;
my $result  = do {
    local *STDERR = $LOG;
    Module2::foo(42);
};

[download]
That's obviously pretty awkward to use small scopes, but you can wrap larger ones - even the whole file - if you like.

With that, Module2 doesn't have to anticipate anything about logging. It only needs to make its complaints to STDERR and it is up to the user to redirect to the log handle.

After Compline,
Zaxo

In reply to Re: Modules sharing? by Zaxo
in thread Modules sharing? by eff_i_g

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.