Evaluating opinions - FilePro Error Messages
Bob Stockler
bob at trebor.iglou.com
Fri Jun 4 07:58:10 PDT 2004
On Fri, Jun 04, 2004 at 12:18:27AM -0400, John Esak wrote:
|
| > I would suggest a way to see all DECLARED VARIABLES, labels, Lookup
| > aliases, Field Headings,
| > Selection sets, array names, (whatever I forgot also) in one alphabetic
| > list, like the declares are listed. Include a
| > code saying which thing it is. That would make it easier to check for
| > conflicts.
|
| An excellent idea. I heartily agree. I would love to see that somewhere in
| *cabe. I would also add an addendum to the problem you had above. The syntax
| checker _should_ disclose and thereby prohibit _any_ use of what filePro
| considers a "protected" word... certainly OPEN would fall into this
| category... but what about processing written before OPEN existed?? and so
| on.
My Perl program "ck.table" (works on UNIX/Linux and Windows)
checks 176 filePro commands (those 3-characters or longer) for
conflict with declared long-name variables, array names and
alias names assigned to real or dummy fields (those are the
only names that mattered, according to my experiments).
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).
More information about the Filepro-list
mailing list