comment on

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

Update: Coding style links, not just sub issues:

A few style suggestions The thread's good, but I like tilly's points

is this correct? Some subroutine pitfalls illustrated

p.s. Nothing like archaeological digs through the monastery. Tends to be a good learning experience.

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks