Re: Noob File::Find issue

Also, not all modules export their subroutines. I have no idea if File::Find does(and I'm too lazy to check), so you might have to do one of the following:

#These statements are equivalent
use File::Find qw( find );
use File::Find 'find';
[download]

I personally find it good practice(by my own conventions) to do that, just to make it clearer to myself where a function comes from. Your choice, ultimately.

~Thomas~ I believe that the source code to life is written in Perl :-)

Comment on Re: Noob File::Find issue Select or Download Code

Replies are listed 'Best First'.
Re^2: Noob File::Find issue by GrandFather (Saint) on May 01, 2012 at 02:14 UTC
If I'm interested in knowing where stuff comes from I do exactly the opposite: `use File::Find qw(); ... File::Find::find(...);` [download] By the time I'm a few dozen lines away from the top of the file I've probably completely forgotten where `find()` came from. A sometimes other benefit of being explicit is that if there is a 'find' in several different modules that are in use then it is clear which one is wanted. True laziness is hard work	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Noob File::Find issue
by GrandFather (Saint) on May 01, 2012 at 02:14 UTC

If I'm interested in knowing where stuff comes from I do exactly the opposite:

use File::Find qw();

...

File::Find::find(...);
[download]

By the time I'm a few dozen lines away from the top of the file I've probably completely forgotten where find() came from. A sometimes other benefit of being explicit is that if there is a 'find' in several different modules that are in use then it is clear which one is wanted.

True laziness is hard work

[reply]
[d/l]
[select]