Hi, grexman,

I like to be able to read code, too, and I've learned most about that subject from this very website.

Encapsulate more of your code into subs. It might make the code run a bit slower (hrdly noticable), but it will be much easier to derive what each section of code is doing simply by looking at the sub calls (assuming you can use descriptive names for your subs). Each of your major comments in your code probably mark good sections to sub-ify.

I was just turned onto the Getopt::Long and Pod::Usage modules, which have made my code infinitely more readable, easier to debug, and much more professional looking. They will add a bit of overhead to the size of your program, but you'll appreciate their benefits, too.

-- ccarden

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.