And if you're using a perl editor that can tell you when you make a mistake by 'misnaming' an undefined variable, lemme know what it is, I'd like to use it. My most common coding mistake is failing to type var names correctly.
One could argue that I should use simpler var names or put all vars and their description at the top of the closure, but while I've never been known as a lazy documenter, I usually only add comments to my code when I'm doing something that is odd or to explain a funky regex.
And strict is something you want to use always. Among other things, it forces you to declare your variable names before using them.
It'll save you time when you debug during development.
As for -w, well once you understand why you should use it, then you know when you can not use it. IMHO, all people in the early stages of perl should use warnings. Once you become more experienced you prolly wont use it as much, if at all.
$0.02 doesn't go as far as it used to, does it?
In reply to Re: Re: Re: Can't get the right array value
by XPWhore
in thread Can't get the right array value
by DaWolf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |