in reply to Re: Its not supposed to!
in thread Its not supposed to!

While there ARE modules out there that will do this, its such a small snip of code I didn't want to bother logging onto CPAN and looking for something that would do the job for me.

Appart from the fact that the name Find::File::etc doesn't suggest what I was trying to do...

The result of this snippet is now being used on my cron to pickup the directories in my /tmp and delete *.htm, *.txt, *.pdf, and files of the sort.

Last time I checked, my /tmp had like 250 megs of sh1t I wasn't using. This keeps me tracking the stuff I really need.

But thanks anyway!

Replies are listed 'Best First'.
RE: RE: Re: Its not supposed to!
by btrott (Parson) on Apr 18, 2000 at 06:32 UTC
    I understand. No problem with writing your own code.

    Although File::Find (not Find::File) is actually in the core distribution, so you wouldn't have to go to CPAN to get it.

[reply]
      No wonder it didn't load! :o)

      But being strictly picky (for this size of operation at least), isn't it cheaper (disk/cpu wise) to do my own small recursion?
[reply]
        But being strictly picky (for this size of operation at least), isn't it cheaper (disk/cpu wise) to do my own small recursion?
        Uh, File::Find is a particularly well-written piece of code, and has optimizations to ensure that it do unnecessary stat'ing (an optimization that made File::Find actually beat /usr/bin/find on Sunos 4.1.3 on an NFS-mounted directory.

        Also, File::Find means your program won't chase symlinks incorrectly (did you think of those?) and your program will be portable to non-Unix platforms trivially.

        So, don't reinvent your own directory recursing code. Use File::Find.

[reply]

In Section Seekers of Perl Wisdom