Help with $File:Find

roperl has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Help with $File:Find by huck (Prior) on Feb 14, 2018 at 18:32 UTC
`push @array, $File::Find::name if (defined $_ && (/^.*\.($TYPES)$/i) +);` [download]	[reply] [d/l]
Re^2: Help with $File:Find by tinita (Parson) on Feb 14, 2018 at 19:27 UTC
It would be interesting to find out, though, when `$_` an actually be undef. I can't find anything about that in the File::Find documentation. I only see a case where `$File::Find::fullname` is documented to be undef.	[reply] [d/l] [select]
Re^2: Help with $File:Find by roperl (Beadle) on Feb 14, 2018 at 18:58 UTC
Ok I was thinking that but I wasn't sure if needed to check if $File::Find::name was defined. So I can write it as: `push @array, $File::Find::name if ( ($_) && (/^.*\.($TYPES)$/i) );` [download] that is they syntax I've been using to check for defined without actually using "defined"	[reply] [d/l]
Re: Help with $File:Find by Marshall (Canon) on Feb 14, 2018 at 20:06 UTC
Your code for `sub get_files` looks a bit odd to me. The reason being that @array is not accessible after the find() operation. Normally you have to declare @array at the same scope as find(). Also, there actually isn't a need for `sub nodirs{}`. You could just have a `next if (-d $File::Find::name);` in the get_files{} sub. I am a bit flummoxed as to how $_ could wind up being undef because this is a file name like readdir() would return. Show us what $TYPES is? There could be something odd in the regex, often \Q$TYPES\E is needed. A a debug thought, I would add: `print "looking at $_\n";` in your get_files routine. I would be astounded if that specific line shows an attempt to print an undef value error.	[reply] [d/l] [select]
Re^2: Help with $File:Find by roperl (Beadle) on Feb 14, 2018 at 21:24 UTC
There is more to my get_files sub that does a foreach (@array) and then checks the files for certain criteria. I left out that section for clarity here. My $TYPES is defined like so: `my $TYPES = 'txt\|gz\|zip';` [download] The only thing I can think of is that the find could be finding a number of files in a directory first and then filling in the names and so if the file is gone in the middle of the operation $File::Find::name will fail because the file name isn't defined.	[reply] [d/l]
Re^3: Help with $File:Find by Marshall (Canon) on Feb 15, 2018 at 01:03 UTC
I and other Monks aren't sure what is happening here. Let's get more info: Add the line `$\|=1;` at the top of your program. This will unbuffer STDOUT. Then put in some print statements as I suggested earlier. Then when the error happens, we will have an idea of what the program was doing. By default, STDOUT is buffered meaning that it only prints when its line buffer is full. STDERR is non-buffered by default meaning that it's error lines print right away. When you un-buffer STDOUT, the time sequence of the normal prints and error prints are preserved. The line right before the error will show what the program was doing right before the error occured. Update: you said "There is more to my get_files sub that does a foreach (@array) and then checks the files for certain criteria. I left out that section for clarity here." It could very well be that your simplification obscures the actual problem. Can you reproduce the problem with your simplified code?	[reply] [d/l]
Re^4: Help with $File:Find by roperl (Beadle) on Feb 16, 2018 at 18:16 UTC
Re^5:Help with $File:Find by Marshall (Canon) on Feb 16, 2018 at 23:09 UTC
Some notes below your chosen depth have not been shown here
Re: Help with $File:Find (rule) by beech (Parson) on Feb 14, 2018 at 21:28 UTC
Hi, Use File::Find::Rule::Procedural Write something like `use File::Find::Rule 'find'; my @files = find( file => name => qr/\.($TYPES)$/i )->in( $DIR );` [download]	[reply] [d/l]