> 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
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.