Thanks! (Um, be sure to post the whole thing... -- I didn't see a line saying "use File::Find" when I read this post.)
Just one concept you should consider: doing a recursive directory search for files of a given type (e.g. *.js) is a very common facility that is handy for a wide range of particular needs -- that's why the GNU "find" utility (and the decades-old unix "find" that it's modeled on) is such a basic, essential component on so many systems (it's been ported to windows, etc).
Even if you want to stick with File::Find (which happens to be a few times slower than GNU "find"), you should consider making it a separate utility by itself, and keep just the editing function in a simpler app that works on a single file, or on a list of files read from stdin -- e.g.:
This way, when you come up with some other particular edit or summarization process to be done on all files of a given type in a directory tree, you don't have to re-write the part that recurses through the directories. Just write a script that will apply the new process to any list of file names on stdin, and use the same front-end program (or GNU "find") to feed it.my_find_utility '*.js' | my_comment_extractor
In reply to Re: Re: Find, read, write out contents of a certain file type recursively...
by graff
in thread Find, read, write out contents of a certain file type recursively...
by Ro
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |