I concur with earlier replies that OO is preferred when you (i) anticipate your code with be reused, (ii) when the code will be used as part of a team development effort, or (iii) distributed in module form.
It is also worth mentioning that, it is a good skill set to acquire if only to improve your familiarity with and ease of use of techniques used by CPAN modules. For many (if not most) Perl programmers, the ability to make ready use of the CPAN is half their value as a Perl programmer.
In general, I think everyone who uses Perl more than casually should take the time to create a module, if only a "Hello World", for the valuable experience it provides.
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.