One program should be one file, unless the "parts" are truly going to be reused by other programs
(which they usually are not)
I hope you're not recommending 14,000 lines of main program in a single file!
On the contrary, I recommend keeping the main program file short, with most of the work
done in (highly cohesive, loosely coupled) modules -- with documentation and a test suite around each module.
You can find many examples of this approach on the CPAN. For example, in Perl::Tidy and Perl::Critic,
the perltidy and perlcritic main programs are not much more than one-liners, essentially just:
use Perl::Tidy;
Perl::Tidy::perltidy();
and:
use Perl::Critic::Command qw< run >;
run();
with all the work being done in (well-documented) modules with test suites around each module.
-
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.
|