I forgot this one-liner, probably because I use it so much it has become almost instinctive:
% perl -cw script.pl
All it does is check for compiler errors and warnings, without running the program.
Why not just run the program? If script.pl doesn't compile, I suppose there is not much difference. Otherwise, it's a matter of "defensive programming." The check above takes one second to perform, and it can alert me to bugs that I may want to know of before ever running the program. Besides, there are times (e.g. when the coding is not yet complete) when all I want is to confirm that my code passes this first test of soundness, but not yet run the code. With a reasonably civilized editor, one can bind this capability to some convenient keyboard shortcut, so one can do the check periodically as one codes, which helps narrow down the location of errors.
-
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.
|
