I bet your code would run a lot faster if you could bypass the filesystem entirely.

Because you can't do that, go for the cleanest interface possible. File::Find loses in this respect.

Personally, I'd rather construct a filter object, add or remove criteria from it, set it to process a directory, and then receive an iterator back in scalar context or a list of matching files in list context.

If you wanted to be really clever, you could return an object for each file that gives the file name when stringified but otherwise contains accessors to other information such as that returned from stat or relative directory names or such... but that may be overkill.

My impression is that making file recursion code that handles callbacks is more complex than most situations need.

---

---

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.