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 `=='.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|