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
use Perl Log In
petdance (2468)
petdance
andy@petdance.com
http://www.perlbuzz.com/
AOL IM: petdance (Add Buddy, Send Message)
Yahoo! ID: petdance (Add User, Send Message)
Jabber: petdance@gmail.com
I'm Andy Lester, and I like to test stuff. I also write for the Perl Journal, and do tech edits on books. Sometimes I write code, too.
andy@petdance.com
http://www.perlbuzz.com/
AOL IM: petdance (Add Buddy, Send Message)
Yahoo! ID: petdance (Add User, Send Message)
Jabber: petdance@gmail.com
I'm Andy Lester, and I like to test stuff. I also write for the Perl Journal, and do tech edits on books. Sometimes I write code, too.
Thursday November 20, 2003
03:52 PM
Code I don't have to write
I love it when I envision a big infrastructure that will be a key component for the project I'm working on, and then finding that someone else has already written it for me.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Log::Dispatch rocks (Score:2, Informative)
Count me among its many fans.
You should also check out Log4perl [cpan.org]. It builds on Log::Dispatch to do for Perl what Log4j does for Java. There are some rough edges, but it's worked very well for me on many large projects.
--Bill
Re:Log::Dispatch rocks (Score:2)
--
xoa
Re:Log::Dispatch rocks, and check out Log4perl (Score:2, Interesting)
Corollary (Score:3, Insightful)
Reply to This