Perl Monk, Perl Meditation | |
PerlMonks |
Re: Confusing warning with if/elsif/elseby radiantmatrix (Parson) |
on Dec 08, 2005 at 15:22 UTC ( [id://515266]=note: print w/replies, xml ) | Need Help?? |
I find it fascinating that you're focusing on the somewhat inaccurate reporting of line numbers that "cost you time", but seem to be glossing over the fact that strict did help you find a mistake. Yes, the behavior of the warning is sometimes strange, and that should (and will) be addressed. But ultimately, strict promises to help highlight mistakes, and it did just that. I'd guess that, overall, you still saved time by avoiding having to hunt down a logic bug later. Update: the downvotes tell me that my tone might be mistaken. I'm not trying to be critical or insulting, I really do find it interesting that a problem that appears to cost in the short run seems to take the focus away from the fact that, despite the annoyance, strict is still a good practice. I posted this to remind novices that the benefits of strictures still outweigh their shortcomings.
<-radiant.matrix->
A collection of thoughts and links from the minds of geeks The Code that can be seen is not the true Code "In any sufficiently large group of people, most are idiots" - Kaa's Law
In Section
Meditations
|
|