IMHO It's less about what is wrong with Log4perl and more about what is wrong with releasing a CPAN module that depends on Log4perl. If WWW::Mechanize::Chrome had been built on Log::Any, this unit test would be able to plug it into (my)
Log::Any::Adapter::TAP and have the log messages be an official part of the TAP stream. Meanwhile people using WWW::Mechanize::Chrome in production could plug it into Log4perl if they want really fancy logging and everyone goes home happy.
Personally I never use Log4perl because I subscribe to daemontools philosophy that all logging of a service should stream through stderr and a separate dedicated logger process should read that pipe and handle all the advanced logic to sort/filter log messages. I like the separation of concerns better than trying to put advanced logging configuration into each perl service.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.