I wrote to Craig Berry:
!Having spent some time yesterday
!poring over the diff between Find.pm
!as shipped with perl 5.8.0 (little difference)
!as well as with perl 5.6.1 (big differences
!due to support added for Mac OS) I was
!beginning to reach the same unfortunate
!conclusion. I guess before we just did not
!have regression tests that had attempted to
!find() their way into a psuedo PERL_ROOT
!hence they had not encountered the SITE_PERL
!logical name before
Oops. I am wrong. File::Find in [EMAIL PROTECTED] does
appear to be "broken", at least on VMS. I tested it by
running a simple find and print script on a directory tree
and ran it under perl 5.005_02 and perl 5.8.1 @19733
and the results differed tremendously.
$ type file_find.t
use File::Find;
print "Using perl $]\n";
find( \&wanted , './mytree' );
sub wanted {
print "$File::Find::dir, $_\n";
}
$ perl552 file_find.t > file_find.out_552
$ perl file_find.t > file_find.out_581
The truly bizarre thing is that 581 does not list certain
files that are in the [.MYTREE...] directory tree, but the script
running under 5.8.1 put more output to SYS$OUTPUT, as
can be determined with a word count perl script:
$ wc -l file_find.out_552
864 file_find.out_552
$ wc -l file_find.out_581
959 file_find.out_581
There should be no discernable difference between
file_find.out_552 and file_find.out_581 in my opinion.
It looks like perhaps a unique filename hash got messed
up in Find.pm as shipped with perl5.8.1.
Peter Prymmer
