[log4perl-devel] $Log::Log4perl::caller_depth, layout %c and %T, and category

2011-01-24 Thread David Christensen
log4perl-devel: I'm a new Log::Log4perl user and am trying to create some Log4perl helper logger functions. I've found that: $Log::Log4perl::caller_depth seems to affect the following layout placeholders: %C Fully qualified package (or class) name of the caller %l Fully

Re: [log4perl-devel] $Log::Log4perl::caller_depth, layout %c and %T, and category

2011-01-30 Thread David Christensen
Mike Schilli wrote: There's a section in the Log4perl manual thattalks about this (not easy to find, though): http://search.cpan.org/~mschilli/Log-Log4perl-1.31/lib/Log/Log4perl.pm#Using_Log::Log4perl_with_wrapper_functions_and_classes Thank you for the reply. :-) Yes, I read that.

Re: [log4perl-devel] $Log::Log4perl::caller_depth, layout %c and %T, and category

2011-01-30 Thread David Christensen
Mike Schilli wrote: We get tons of spam on this list, so it's moderated. That's what I thought. I'll post to the list and BCC you. What you want to do instead is use the long form with get_logger(): package Helper; use Log::Log4perl qw(get_logger);

Re: [log4perl-devel] Log::Log4perl best practices

2011-09-28 Thread David Christensen
On 09/26/2011 10:14 AM, Mike Schilli wrote: Actually, :easy mode macros and get_logger() are identical in function, the difference is just typing convenience. I personally use :easy macros like DEBUG and INFO in conjunction with log4perl configuration files, unless for really simple scripts