more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
At work we're examining Log::Log4perl as a logging system (as my previous post indicates). As I evaluate the module, I get the sense I'm not using it well, as I feel it wants to spread like kudzu
through our entire project. I want to put a wrapper around it, but am not sure how to do that, as it is a singleton.
Here's why it seems like kudzu. Each script is starting out with something like this then each module needs to start out with Should there be this much overhead? When I see all this repeated code, I don't like it. This adds 4 lines to each program (not a big deal) but it also adds 4 lines to each .t script (?!?!) and 2 lines to module... surely it shouldn't require this much repeated code? Thanks for any ideas In reply to Log::Log4Perl best practices by water
|
|