The absence of strict, warnings, and taint don't necessarily imply a bad script.
in reply to Re^2: [off-site] Perl snippets at Microsoft
in thread [off-site] Perl snippets at Microsoft
No, it doesn't. Each is useful for different purposes.
- strict is useful is you plan on ever making a change to the thing as it will decrease the time you need to do so safely.
- warnings is useful is you are a less-experienced developer.
- taint is useful if you are taking information from an untrusted source.
Of these three, I would add strict and taint. Warnings are ... annoying in production code. I take it out in my CPAN stuff. I would add taint because I'm not sure what Win32::OLE is going to return to me. I'd like to see if Perl trusts it before I do.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.