Commands Possibly Using filePro File Names

[Bob Stockler]

On Thu, Mar 31, 2005 at 05:46:54PM -0500, Brian K. White wrote:
[snip]
| You'd have to do what a person does when reading the code: Notice that the 
| lookup target is a variable and backtrack how the variable gets filled, 
| which would ultimately probably require a large chunk of clerk or report or 
| cabe before it really worked.
| 
| One reason you were right to start out by only looking at commands that 
| take filenames as arguments, was because of all the ways the exact same 
| string as filename might appear that aren't filenames and shouldn't be 
| touched.
| 
| You can have lookup INVOICE and getenv("INVOICE") and form "INVOICE" and 
| screen "INVOICE" and declare INVOICE and a real field could be named 
| INVOICE and referred to by it's name instead of it's number and input aa 
| "INVOICE: " etc ad nauseum...

It's not so complicated as that.  I'm dealing with a known system
where the filePro File Names that need to be changed are known to
be entered as literals in the processing tables.

In my AWK program I build a regular expression that matches only
the file names of interest, so only has to act on matching lines.
On lines of interest it loops over all the Old Names (in an order
where no conflict will arise) and subsitutes the New Name for the
Old one.

A similar AWK program edits filePro User Menus and their scripts.

All have been tested and work, and do so efficiently.

Bob





-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).