There doesn't appear to be a way to force perl to be
strict about all your code, but there is an easy way to
work through it incrementally. What you could do is test
each module, fix any serious errors, and then catch the
minor ones later when you have time.
You can "test" the modules by running them, such as:
% perl -w -Mstrict Some_Module.pm
This will generate a whole bunch of errors and warnings,
or, if things are cool, it will presumably do nothing at
all (unless the module actually does something by default).
Once you're done, or merely tired of fixing all the bloody
errors, you can just run the program normally, whatever
that means.
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.