Try to section your programs into stand-alone chunks. Turn these chunks into subs; try to test each for all possible inputs and behaviors. Once a sub works, you can use it as part of bigger and bigger sections of your program, each of which should be tested in turn.
As far as standard formatting goes, always write your programs for use strict and use warnings; define all variables at the top of the section that uses them; insert comments wherever you're likely to have problems remembering the mechanics of your code later. Use some sort of standard naming scheme for variables and subs that avoids case sensitivity problems and name collisions.
Read through the posts here every day and try to solve the algorithmic problems on your own. Then compare to posted code. My code formatting got worlds better within a week or two of doing this.
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.