Warnings and Strictures should only be used during development. They don't really serve a useful purpose in production code.
I totally and utterly disagree.
Warnings and strictures are there to catch and prevent errors during development and help you trace errors in production. Seeing that a previously warning free script all of a sudden starts generating warnings is sign of a serious bug that should be resolved immediately. Disabling warnings and strictures would mean that you never knew a bug existed.
Specifically disabling specific warnings or strictures for limited scopes of your code is perfectly ok. Turing off warnings and stricutres in code that was written with it (most of CPAN) is irresponsible and dangerous.
I have been witness to several sites exposing their DB access username/password once a fatal error occurs.
So because these sites did something foolish you advocate removing your ability to see that the program is doing something unexpected? That doesnt make sense to me.
In reply to Re: Re: Re: Re: How many security holes can you find?
by demerphq
in thread How many security holes can you find?
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |