Modules don't have to be of general (read generic) use only. The purpose of modular design, is to make difficult things easier. That can mean code reuse, or any of a number of other reasons for modularizing your code.
If your difficulty is too big of a program file (more than a few hundered lines, give or take), it may be time to factor some of the code out into modules. One of the beauties of this approach is that once you have the details of a module hammered out, you can consider it "done", and move on to working on other sections of code. At that point, so long as you stick with the module's interface, you usually don't need to worry that a change somewhere else in your script might ripple a problem into the other module.
Modularity isn't just about code reuse. It's also about namespace segregation, divide and conquer coding, and keeping code chunks bite-sized for easy digestion. (and object orientation, and, and, and....)
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.