Greetings,
I'm probably missing something obvious here, but it seems
counterintuitive to me to have
#!/usr/bin/perl
use strict;
use Log::Log4perl;
my $config = '/dev/null';
eval { Log::Log4perl::init($config) };
die "Log::Log4perl::init failed:$@" if $@;
if ( Log::Log4perl::initialized() ) {
Log::Log4perl::get_logger()
->logdie("hmm, log4perl thinks it's been
initialized");
}
die "log4perl isn't initialized";
pass the eval() and then logdie() using an uninitialized logger.
Wouldn't it be better to move line 113 in Config.pm
$Log::Log4perl::Logger::INITIALIZED = 1;
to the end of Log::Log4perl::Config::_init(), after L4p has been
successfully initialized?
Thanks much.
Log::Log4perl/1.13, perl 5.8.0, RHEL ES3/Taroon
Log::Log4perl/1.12, ActiveState perl 5.8.8/bin822, WinXP/SP2
--
Rob Raisch, Financial Media Holdings Group, Inc.
Publishers of "Compliance Week" -- http://www.complianceweek.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
log4perl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/log4perl-devel
