The
apparently arbitrary restrictions, are very far from being arbitrary.
There's nothing wrong with using modules (I
use many myself),
but as a perl nub, an "I want X done" isn't my entire interest, but a more "how does it work" wondering,
both for theoretical and practical purposes.
Also the more fundamental the code is, the greater its implementation potential is,
the less likely it is to surprise the user (by run/intent errors), and the easier it is to be customize to the exact desired purpose for which it is required.
A less common reason to avoid modules (I faced) is when planning to convert the pl file to something else (like exe) once it's done,
but your converter can't handle modules correctly.
Generally when writing a long and complicated program, a module can be a huge time (& headache) saver,
but whenever using a module can be avoided (with a reasonable cost), a diy is always my choice.
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.