modules ++

frivolous module use --

mom and apple pie ++

Seriously, we favor two kinds of modules --

• objects -- with encapsulated data, public & private methods, and numerous unit tests,
• exported subroutines -- with complex behavior, no side effects, and numerous unit tests

In both case, wrapping it up a module allows cleaner code, easier refactoring, and better documentation. Consider something like this

if (! &valid_foozle_input($wozzle)) {
[download]

versus

if ($wozzle =~ /extensive-perl-regexp-line-noise-here/ {
[download]

The former clearly indicates what is going on, the documention on what makes something fozzle_valid can go into the module (sub or object, depending), you can now write unit tests against the sub, you can use the sub in numerous places across the codebase (instead of just in this file, as a local sub would require), not have repeated code, etc.

just my two cents -- your mileage may vary

water from the great white north

---

---

• 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.