A friend of mine writes all his code as though the -T switch was turned
on: he tests all user input, cleans the environment, so on and so forth.
Then, when he thinks he's done, he runs the code under -T to see if
there would have been problems.
This doesn't find all bugs in all code, but it appears to help---many
subtle bugs can pop up in Perl because of incorrectly checked user input.
Personally, I prefer to cut and paste the code somewhere else, (or check
it in to a branch with CVS or RCS) and rewrite what I think is incorrect.
This helps me find stuff like testing for equality with `=' or `eq'
where I should have used `=='.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||