in reply to Re^2: Avoiding silly programming mistakes
in thread Avoiding silly programming mistakes
It's a fair bet that the OP won't repeat the DESTROY mistake again for a while and it's a much better bet that strictures will pick up silly errors way before the repeat of the DESTROY error.
The dogma are dogma because they are valid and relevant to many of the problems people bring to PerlMonks. There is a chance that a first poster here hasn't met them before and even if the OP uses strictures, it is another safe bet that someone reading this thread in the future doesn't use strictures and will benefit from them.
Strictures aside (it seems you may not have not have noticed the smiley), I offered advice on a number of levels to address a range of issues. There are no panaceas that resolve all such issues and nothing can prevent typing the wrong character in the first place, but tools that catch common errors early help a lot.
CPAN is a huge resource. It contains a fair amount of dross for sure. But it also contains a huge amount of well written, well documented and tested code that is widely used. That's a heck of a lot of code that you don't have to write. Yup, there are probably bugs in every CPAN module, but if you can write equivalent code that is bug free despite 'still making "doh" mistakes' then get out and publish!
Perl reduces RSI - it saves typing
|
|---|