I have to disagree. I think no warnings 'uninitialized'
is a much more elegant way to avoid those idiotic warnings. For one thing, they shouldn't be warnings in the *first* place. In this example, the expression that triggers the warning is:
60 * undef
Why should this cause a warning? The behavior is well-defined, documented, rational, and well understood. I don't think perl should be warning me about this since it is a feature of Perl!
Your solution (nothing personal, its a common workaround) converts the above expression to:
60 * (undef || 0)
Which doesn't spew out a warning... The question is why not? If the first one gives me a "Use of uninitialized value in multiplication" error, why wouldn't this give me
a "Use of uninitialized value in logical OR" error? Its not like undef in boolean context is more well-behaved than in numeric context1
. Why should one throw a warning and the other not... Either both should trigger warnings and we sprinkle lots of defined()
calls everywhere, or neither should.
Adding gratuitous logic to avoid spurious warnings doesn't agree with me. Better just to turn those specific warnings off and be done with it.
1I know thats splitting hairs, but the fact that it is splitting hairs is kind of my point anyway.