in reply to Log4Perl configuration problems

As a sidenote here, if you think a given distribution has lousy docs, and you have any choice in the matter, you should probably email the maintainer (with constructive criticism) and then not use said module if there's no improvement.

Silently using modules with bad docs sends the message that docs don't matter because you'll use the software anyway.

Replies are listed 'Best First'.
Re^2: Log4Perl configuration problems
by ribasushi (Pilgrim) on Jun 13, 2008 at 13:44 UTC
    Generally you are correct, however this module is ahead of the crowd by leaps and bounds. The design is too good to pass on it over documentation issues. It's like saying "I won't use IO::Socket because the docs suck".