A simple rationale is that if you want to print $flag for debugging, "undef" is an error
How come? Last I looked it was a warning, and only if warnings are enabled.
Additionally it's a good idea to use Data::Dumper or something similar for debugging output anyway, so I don't see the point you're trying to make.
Another rationale would be that you KNOW that it is "false" not "undefined"!. So say so!
undef is also false - why would 0 be clearer false than undef? 0 is a number to me, not primarily a "false" boolean value.
In reply to Re^2: Looking for less code
by moritz
in thread Looking for less code
by Sun751
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |