Your code is very difficult to grasp for the following reasons. It is also failing for at least one of the following reasons:

• You have no indenting, which makes it really hard to visually grasp where loops, blocks, and subs start and end. This not only makes it difficult for us to comprehend, it makes it difficult for you, the programmer, to keep things straight.
• You are defining named subs within loops. This is a "bad idea." It probably doesn't do what you think it does. In fact, if your subs were rewritten to avoid using global osmosis, it's approximately the same as defining the sub just one time somewhere outside of the loop, and that would lead to clearer code too.
• You are passing values and variables into subs from higher lexical scopes (similar to using global variables to pass values into a sub). This makes readability very difficult, and in your case may be introducing a closure bug (see next item).
• Even though your subs are being defined within a loop, my assumption is that the 'my' variables available to them from outside the sub's brackets are the ones that occur on the first iteration of the loop. When that first iteration ends, the scope closes and all subsequent iterations will not work as you intend.

Pass all variables and values into your subs through @_, not through global osmosis. Define your subs outside of the loop. Your final use of 'last' seems to be useless.

I may be missing the mark on scope closing around the subs after the first iteration of the loop, but if I'm right about that, there's your biggest problem. One of the very few legitimate reasons to use a variable from a broader scope within a sub is to set up an intentional closure. I don't think you're intentionally doing that. Instead, it's an unintentional consequence of the way you've got your code structured.

---

---

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.