If there are holes in your test scripts, then they are not testing everything you deem important! If you can't trust your test suite to test your scripts and modules, then what can you trust? A hit-and-miss perl -c approach will be unlikely to pick up any more bugs than your tests. If you don't think your tests are good enough, I'd get intimate with the relevant incompatible changes in the perldeltas (a quick search on your scripts for threads and unicode might not go amiss); then install your modules and scripts on a dev box, and run them into the ground with automated tests. Whenever you find a bug, add it to the test suite, and that's one less thing you need to do manually next time. Best of luck with it.
-
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.
|
