I agree with the sentiments expressed here, including the use (not mentioned) of use warnings. Basically, I think, the idea is to force as many dumb mistakes to be detected “at compile time” as possible. When you are writing thousands of lines of code, little will typos creep in that you didtn recognize at the time. And the time that you want to detect those isssues is, right now. The computer has the amazing ability to detect the slightest inconsistency, and you want the computer to be doing everything in its power to assist you in that regard. It will never encounter “Paris in the the spring” without instantly flagging the extra “the.” But did you, while reading this, encounter every one of the five tpyos I put in here? (If your browser underlined them for you, it doesn’t count.)
If you find that you must use a construct that flags a warning, you can use the no construct, and liberal and detailed comments, to explain exactly what you are masking-out and exactly why. (You will not remember, even with regard to your own code.) Then turn the feature right back on as soon as possible.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||