Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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 class sorta thing that handles the calls.

    I have a private application which does this about half way. The application basically uses the same interface (trace, debug, warn, etc) methods, but it autoconfigures at the beginning. It's a big pile of crap because it's half done and my first idea on how to do it, but someone probably has a good idea.

    However it works out, I think both packages are nice and I don't want to make other people choose. I like Log4perl, but that's just because it does what I want and I don't need to do any more.

    • 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…