I tend to agree that loading seventy modules seems a little excessive; however, where do we define the cut-off point?
Why does it seem excessive? Is 20,000 lines of code excessive? Now if you said 70 modules just to print "hello world" on the screen, yes, that would be excessive, but 70 modules to walk on water?
70 modules to save yourself years of work at the cost of 7 seconds startup time?
Hardly excessive.
Somebody pointed out to Dominus http://simon-cozens.org/draft-articles/email.html, Simons thoughts on the design of Mail::Box.
So Mail::Box is ripe for refactoring, so what?
I wouldn't care if it loaded 150 other modules.
It does many things and I didn't have to write it.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
-
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.
|
