You're absolutely right: the glob replacement is incorrect. Worse, it worked "close enough" that I managed to think I had done it right. I appreciate you pointing that out, I'll work on fixing that.

To be perfectly honest, building regexps on the fly seemed clever at the time, but I'm not really sure it bought us that much. I was thinking in terms of typical shell usage, where *.conf refers to any file ending in ".conf". But the reality is, /\.conf$/ matches that already, with no need to explicitly name a wildcard. Additionally, I ended up using anchors in the strings, which is precisely what I was trying to avoid.

In reply to Re^2: File finder by mpeever
in thread File finder by mpeever

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.