Others may have technical reasons for preferring one over the other, but for me the differences are primarily in clarity and esthetics. (A) is more concise and thus the logging does not clutter the main flow of code as much. I also expect logging to be a global resource, at some level, so I wouldn't be looking for logging connected to each instance. If I found it in each instance, as in (B), I'd then be on the lookout for some specific purpose that made instance logging necessary. (I'd be mildly uncertain about my understanding of the code if I never found one, and mildly annoyed if I found that there definitely was no specific purpose.)

In reply to Re: Log::Log4perl use strategies by rodion
in thread Log::Log4perl use strategies by Excalibor

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.