I never switch off use strict
but I used to disable use warnings
for production code (but only after it ran clean of course).
Nowadays I always use Modern::Perl with enables both strict and warnings and I do not bother with disabling it anymore in production code. In rare cases I might locally disable irrelevant but well understood warnings for unititalized variables.
I use Perl mainly for transforming data from one format to another and when an unexpected "unitialized variable" warning crops up, it ususally means that there is something wrong with the data and the parser I wrote has failed to match some data to a variable, hence the warning. I think this warning is a nice last resort catch-all line of defence and I would not want to miss it.
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
My blog: Imperial Deltronics
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||