Re^3: listing all subdirectories of directory into file

I would agree that File::Find is more useful, more powerful, and more productive.

However, it has some requirements/expectations of the user. It requires the user to understand callbacks, depth-first vs. width first, How to get the current directory name - all of which you can get if you RTFM, but IMHO, it is conceptually fairly difficult to ingest, for a newbie. That was my reasoning behind recommending 'opendir'. Also, once someone has gone through that pain, it is easier to appreciate a fine module like FF and FF:Rule.

I hope life isn't a big joke, because I don't get it.
-SNL

Comment on Re^3: listing all subdirectories of directory into file

Replies are listed 'Best First'.
Re^4: listing all subdirectories of directory into file by sauoq (Abbot) on May 26, 2012 at 06:38 UTC
It requires the user to understand callbacks, depth-first vs. width first, How to get the current directory name Ah, but if you are going to roll it by hand, you should probably understand depth vs. breadth first searching. And certainly how to get the current directory name. You might also want to know a thing or two about symlinks and symlink loops, and think out your error handling. And, really, if you are going to do all that, there's a good chance you understand callbacks already. (BTW, I don't know how much you really need to understand about callbacks to follow an example and use one; not that I advocate using something that you don't understand... but you gotta learn somehow.) `-sauoq "My two cents aren't worth a dime.";`	[reply]

Replies are listed 'Best First'.

Re^4: listing all subdirectories of directory into file
by sauoq (Abbot) on May 26, 2012 at 06:38 UTC

It requires the user to understand callbacks, depth-first vs. width first, How to get the current directory name

Ah, but if you are going to roll it by hand, you should probably understand depth vs. breadth first searching. And certainly how to get the current directory name. You might also want to know a thing or two about symlinks and symlink loops, and think out your error handling. And, really, if you are going to do all that, there's a good chance you understand callbacks already. (BTW, I don't know how much you really need to understand about callbacks to follow an example and use one; not that I advocate using something that you don't understand... but you gotta learn somehow.)

-sauoq "My two cents aren't worth a dime.";

[reply]