Just a couple comments on the coding style I have seen you use in many of your posts.

• my is a token separate from the name of the variable. Whitespace can help with readability. The formatting that you seem to prefer (my$var ...) is not one that I typically see, is unexpected, and (at least for me) causes a break in the flow while mentally parsing the code. More typical is my $var ....
• When assigning to a hash, it can be more readable to write %hash = ( a => 1, b => 2, c => 3, ... ). The 'fat comma' is another indicator to my synaptic-based parser that this is a hash assignment.

Nothing that is end-of-the-world type stuff, but more indicators to help my future-self understand what I was thinking when I originally wrote the code.

---

---

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.