Re: Re: Perlmonk's "best pratices" in the real world

[cchampion]

I too throw out all the 'best practises' from time to time because they do slow down development

I fail to see how strict and warnings could slow down your development. I would say it's quite the opposite. Without strict and warnings it takes longer to realize where the mistakes lie, thus increasing your development time.

[EvdB]

I mean this in very limited circumstances such as:

perl -e '$a = "abcde"; print ($a =~ m/a.c/ ? "hit" : "miss");';

If it ever goes into a file then use strict, use warnings is ALWAYS there at the top. ALWAYS.