Commands Possibly Using filePro File Names

[Brian K. White]

----- Original Message ----- 
From: "Bob Stockler" <bob at trebor.iglou.com>
To: "Fplist (E-mail)" <filepro-list at lists.celestial.com>
Sent: Thursday, March 31, 2005 9:58 AM
Subject: Re: Commands Possibly Using filePro File Names


> On Thu, Mar 31, 2005 at 09:43:52AM -0500, Ken Brody wrote:
> | Quoting Bob Stockler (Thu, 31 Mar 2005 09:29:42 -0500):
> | [...]
> | > You don't understand the problem.  I want to change nameA to nameB,
> | > nameC to nameD, nameE to nameF ... nameY to nameZ, so I can skip
> | > the processing that does that on processing table lines that can't
> | > possibly have a filePro File Name on them.
> | [...]
> |
> | I guess you really need to further define "can't possibly have a filePro
> | file name".  After all, what about this:
> |
> |     MyPath = getenv("PFDATA") & getenv("PFDIR")
> |     MySelSet = MyPath & "/filename/sel.newsel"
> |     ...
> |     export ascii sel = (MySelSet) r=\n
> |
> | or
> |
> |     MyLibPath = getenv("PFDATA") & getenv("PFDIR") & "/filepro/Library/"
> |     ...
> |     call MyLibPath & "mylib"
> |
> |
> | Oh, and I forgot READSCREEN, READOUTPUT and SORTINFO.  (Or were those on
> | your original list?)
>
> You're right, it's more complicated than I thought.  I was
> going about it bassackwards anyway.  It's even easier, and
> more economical, for me to build a regular expression that
> matches all of the filePro File Names of interest, doing
> the grunt work on those matching lines alone.
>
> Bob

File names could also be built dynamically but I don't see a way to detect 
that.
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...

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani