I'm not sure what you trying to match, you say the user can enter either the literal string "/" or the regular expression /\/w+/ but then test for neither.

m|\x2f{1}?| is just an obscure way of sayingm|/| which is not the same thing as $fs eq "/". The g modifier seems unnecessary. The next test checks for input that doesn't match /\/w+/.

I will guess that you don't want to prune if the directory path has a '/' and do otherwise.

find_me( $fs, $fs =~ m|/| );

sub find_me {
    my @directory = shift;
    # play nicely with others
    local $File::Find::prune = shift;
    <snip>
}

[download]

In reply to Re: file::find question by hipowls
in thread file::find question by mikejones

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.