It might be easier to process the directory tree in two passes. I'm thinking something like the following might work:
#!/usr/bin/perl
use warnings;
use strict;
use File::Find;
my %targetdir;
my %visiteddir;
sub wanted_stage1 {
return unless -f;
$targetdir{$File::Find::dir}++ if /\.old$/;
}
sub postprocess {
return unless $targetdir{$File::Find::dir};
return if $visiteddir{$File::Find::dir}++;
print "Changing files in $File::Find::dir\n";
}
# build list of directories containing *.old files:
find({wanted => \&wanted_stage1}, ".");
print "Directories to process: @{[sort keys %targetdir]}\n";
# process files in directory list:
find({wanted => sub{}, postprocess => \&postprocess}, sort keys %targe
+tdir);
__END__
.:
code.pl
code.txt
one
two
./one:
bar
foo
three
./one/three:
four
something.old
./one/three/four:
blah
something.old
./two:
bar
foo
something.old
Directories to process: ./one/three ./one/three/four ./two
Changing files in ./one/three/four
Changing files in ./one/three
Changing files in ./two
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|