You might want to collect the desired file specs by accepting arguments that point to a text file that lists all the files that the user wants modified(because they are scattered about the file system) and/or a combination of path/wildcarded filenames from the command line etc... .
That way you only have to worry about code in one place to maintain.
Take a look at Getopt::Long for some ideas about what you might want to do regardless of whether you do the wrapper or incorporate the code in the main script.
Hope that is helpful...
In reply to Re: A small wrapper
by wjw
in thread A small wrapper
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |