OTOH thanks for the "eval" advice but in my camel book performance chapter 24 point 6 it says avoid eval on a string and in a loop. Here we're doing both. So now i really wonder who i should believe, some anonymous guy on a forum or a book written by Larry Wall . Gee, that's a tough one ...

If you've already decided to take the advice of Larry Wall, why did you bother to ask?

Also your understanding of IO is wrong : it's much more likely that the module data will already be in memory since we have a lot of files to process for each module function.

Yeah, whatever. It's always useful to not tell important details of the problem you are enquiring about, and to be bitchy if an answer you get didn't consider this detail.

---

---

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.