> 14000 lines of working code is no joke. Why bother refactoring?
Such monster are mostly full of bugs because maintenance becomes impossible if you've lost the overview.
Let's be generous and assume 100 lines of code and clutter per function in average. That'll mean 140 functions...
... divide this by 5 or 10 or 15 ...
> K.I.S.S.
D.A.C.D. °
Splitting up into smaller units, included with do or require is pretty safe˛ ...
and will add
- far better overview already.
- easier POD-Documentation
- better control over global vars
- granulated revision control by changing single files instead of a whole bundle
- easier deployment
- more efficient testing
and I haven't even talked yet about the possibilities to improve this code further like described in my first post.
°) Divide and conquer, Dumbo!
˛) file scoped lexicals must be in the same file like the functions they access
-
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.
|