in reply to Re: Splitting program into modules
in thread Splitting program into modules
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
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
|
---|