Re: [log4perl-devel] invoking threshold() leaves appender data inconsistent

2010-02-07 Thread Mike Schilli
On Fri, 29 Jan 2010, Rob Retter wrote: > But when your application does: > my $wrapper = $Log::Log4perl::Logger::APPENDER_BY_NAME{'somename'}; > $wrapper->threshold ('INFO'); > what you get is the wrapper object's "level" field set to the... um, > priority of the 'INFO' level you passed in. The

[log4perl-devel] invoking threshold() leaves appender data inconsistent

2010-01-29 Thread Rob Retter
After plunking (actually, single-stepping in the debugger) around the marvel of appender wrappers, appenders, closures, levels, thresholds, and priorities that is Log4perl, I noticed the following. As the Log4perl doc says, under "Access Defined Appenders": "The previously mentioned method append