I have never used File::Find or any of its cousins, so take my comments with a grain of salt. I don't do much filesystem work, so I rarely need to deal with files. When I have, a simple glob worked nicely.

I have looked at File::Find before, but quit reading after the first few lines of the POD. It was making easy things difficult. IMHO, a module that deals with something as basic as finding files should

File::Find fails both those tests.

Additionally, I would think that one of those interfaces should be an iterator. Whether or not you pass some set of rules in to the finder, iterators are just plain useful.

As for subrefs, map, and the like - that's a separate question. Callbacks are a non-trivial concept, and should be treated as an upper level in programming (at least how programming is taught in most places). That File::Find requires this interface is just another reason why it's not well designed.

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: File::Find considered hard? by dragonchild
in thread File::Find considered hard? by Jenda

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.