Thanks
I got it to work both ways. I will use File::Find in practice as it performs
much better.
Thanks for your help.

> -----Original Message-----
> From: Maxim Berlin [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 28, 2001 5:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re[2]: Help with Recursive script on Large Directory
> 
> 
> Hello James,
> 
> Tuesday, August 28, 2001, Kipp, James <[EMAIL PROTECTED]> wrote:
> KJ> Thanks so much for your help. Is this how the code should 
> be before I test
> KJ> it again.
> 
> It depends of your needs. for example, in your log file you miss full
> name of files.
> a good example or educational purpose, but in real life, please use
> File::Find.
> 
> KJ> use Cwd;
>         
> KJ> $log = 'c:\\temp\\chk_space.txt';
> KJ> $path = 'dbm\\marketing_database_II';
> 
> open(LOG, ">>>$log") or die "Can't open $log: $!";
> KJ> print LOG "These files are over 60 days old and over 50MB\n\n";
> 
> KJ> ScanDir($path);
> KJ> ## why not &ScanDir($path)??
> see perldoc perlsub for detailed explanation about differences between
> (example from perlsub)
>            &foo(1,2,3);        # pass three arguments
>            foo(1,2,3);         # the same
> 
>            foo();              # pass a null list
>            &foo();             # the same
> 
>            &foo;               # foo() get current args, like 
> foo(@_) !!
>            foo;                # like foo() IFF sub foo 
> predeclared, else "foo"
> 
> you do not need that &, so don't use it, it's dangerous.
> example:
> --------------------
> sub a
> {
> print "sub\n";
> }
> 
> print "test"
> &a;
> --------------------
> i've missed ';' after 'print "test"', and now i got
> 
> print "test" & a;
> 
> construction. very difficult to find.
> 
> 
> Best wishes,
>  Maxim                            mailto:[EMAIL PROTECTED]
> 
> 
> 
> -- 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to