I endorse chromatic's comment.
When writing scripts, I typically abstract the work they do into CPAN-like modules
and unit test each module using Test::More and the prove command.
I strive to keep my script mainlines as short as is practicable.
There are many examples of this approach on the CPAN;
see, for example, the perltidy command, part of the Perl-Tidy distribution
and the perlcritic command, part of the Perl-Critic distribution.
See also:
Effective Perl Programming, 2nd edition: Item 91, "Write programs as modulinos for easy testing"
-
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.
|