Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
> 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.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

°) Divide and conquer, Dumbo!

˛) file scoped lexicals must be in the same file like the functions they access


In reply to Re^2: Splitting program into modules (Divide And Conquer) by LanX
in thread Splitting program into modules by lis128

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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, 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, 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others perusing the Monastery: (5)
    As of 2019-09-21 09:27 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      The room is dark, and your next move is ...












      Results (271 votes). Check out past polls.

      Notices?