NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
How can we support both? (Score:2)
I've been thinking a lot about the same thing, and I'd really like to see something like an agnostic logging interface where users could use either as they liked, just as DBI does for databases.
I'd like to put in logging calls into my modules, but without a dependency on any logging module. If an application uses Log::Dispatch, my module level calls get converted into Log::Dispatch things. If they use Log4perl, then my module does the right thing for that. If they don't use either, there is a default null
Re:How can we support both? (Score:2)
I'd really like to see something like an agnostic logging interface where users could use either as they liked, just as DBI does for databases.
Be careful what you wish for. I've been doing lots of Java recently and exposed to the pain of commons-logging [apache.org]. I wouldn't want to see that repeated…
Reply to This
Parent