I've always liked the "If it's a routine that takes up
more than a page, break it into subroutines"
Though I really follow
Redundent areas get put into subroutines
Use descriptive names for your subroutines so that it should
be intuitive what they are doing. Comments can help as well
Coding style links, not just sub issues:
Suggestions for working with poor code
Silly code reviews and shift
A few style suggestions The thread's good, but I like tilly's points
is this correct? Some subroutine pitfalls illustrated
Call Subroutines by Approximate Name No help, but amusing
Monk ethics: Beauty vs. Power
A question of style
Another commenting question, More on commenting
p.s. Nothing like archaeological digs through the monastery.
Tends to be a good learning experience.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||