Posted by Jacob Bachmeyer on Nov 16 That is because Perl's undefined value coerces to an empty string and/or the number zero, with a "Use of uninitialized value" warning if warnings are enabled. (This is part of the reason you should always put "use strict; use warnings;" at the top of every file of Perl code.) Since both of those are also Boolean false in Perl, the undefined value is accepted (without a warning) as a false value in Boolean contexts

Read the full article at oss-security →