On 09/28/2011 11:04 PM, Mike Schilli wrote:
> If you want to bump up the caller level, you should be using
> wrapper_register() or $Log::Log4perl::caller_depth as explained here:
> http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl.pm#Using_Log::Log4perl_with_wrapper_functions_and_classes
Y
On Wed, 28 Sep 2011, David Christensen wrote:
> Ok. I've upgraded my wrapper functions to use caller() when calling
> get_logger().
That doesn't sound right.
If you want to bump up the caller level, you should be using
wrapper_register() or $Log::Log4perl::caller_depth as explained here:
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 scrip
On Sun, 25 Sep 2011, David Christensen wrote:
> I'd like to upgrade
> everything to whatever is consider best (or better)
> practices.
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 I
log4perl:
I started with Log4perl a few months ago and wrote some modules that use
Log4perl in easy mode with no get_logger() categories. I'm now working
on more modules and an application that uses Log4perl configuration
files and get_logger() categories. I'd like to upgrade everything to
w
