Step one, check all of the code into a reliable version control system. Accept nothing less capable than Subversion (darcs, git, bzr, svk, and p4 should all be fine). If you don't know how to use a revision control system, learn.
Step two, run Perl::Tidy over all of the code per your preferred rules. Check in the new versions. Make sure they still compile with perl -c and check any perltidy.ERR files.
Step three, Perl Medic should have arrived by now. (Order it as step zero. Do not skip this step; it is an excellent book written well by a very capable programmer and everyone should read it.) Follow its steps.
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.