I tested with:

find(\&wanted, "/usr/home/amarquis");

sub wanted {
    print $File::Find::name . "\n";
    if ($File::Find::dir =~ /images/) { 
        $File::Find::prune = 1;
    }
}

[download]

And indeed it continued to call wanted for files in "images" but did not go into subdirectories. But since you already have in place a check to see if you want to prune a directory, why not extend that check to before you process a file? For example:

sub wanted {
    # Prune this directory so we don't recurse farther,
    # And return so we don't process this file.
    if ($File::Find::dir =~ /images/) { 
        $File::Find::prune = 1;
        return;
    }
    # Now we can do our processing:
    print $File::Find::name . "\n";

}

[download]

In reply to Re: File::Find::prune problems by amarquis
in thread File::Find::prune problems by spx2

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.