If you suspect a problem with the regex, the first thing I would do is get rid of the g modifier. I'm not saying it will solve your problem, but it does seem out of place. Also, Tip #9 from the Basic debugging checklist recommends using YAPE::Regex::Explain to demystify regular expressions.

If you could re-create your problem with some self-contained code and data, it would be something we could run. As it stands, you are reading in multiple files which we do not have access to.

Here are some other things that look suspicious to me:

• You use your input lines as filenames without chomping them first.
• You are using $_ in different places inside nested while loops. It might be easier to use a different named, scoped variable for each loop.

Also, I recommend commenting out use diagnostics; when you are done debugging.

---

---

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.