On Tue, 23 Nov 2010, Kevin Goess wrote:
> Any opinion on this? Or should we stay with the uninitialized
> warning, however unhelpful it is?
I'm in favor of getting a warning in this case, at least with 'use
warnings' mode.
It's similar to
use warnings;
print "The value is $value.\n";
This is kind of annoying thing that I noticed recently, if you do
$logger->info($msg) and $msg is
undefined then you get a warning:
perl -W -Ilib -e 'use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init($INFO); INFO(undef)'
Use of uninitialized value in join or string at lib/Log/Log4perl/Appe
