case insensative ambiguity between labels and long variables ?

[Bob Stockler]

On Mon, Jul 11, 2005 at 05:55:33PM -0400, Brian K. White wrote:

| Would you say I should or should not be able to do this?
| 
| report processing
| 
| 
| -------top of table-------
| ...
| withpod: if: WithPOD eq "Y"
| then: stuff
| if: withpod
| then: stuff
| ...
| end
| @once
| if:
| then: WithPOD = "N"
| if:
| then: input popup WithPOD "Include POD? \GZ" DEFAULT "N"
| if:
| then: end
| if:
| then: declare WithPOD(48,*,g)
| -------end of table-------
| 
| Originally that table worked fine with the long variable and only one line 
| of code conditional on it, and no "withpod" label
| 
| When I went to add another line of code that hinges on WithPOD, I added the 
| label to end up with code like above.
| 
| When I went to save it it gave me a syntax error on the withpod label 
| saying that it's already used. withpod does not appear anywhere else as a 
| label, or anywhere else at all in all lower case except where you see it 
| above in the if: test.
| 
| Easy to work around of course but as far as I'm concerned there wasn't any 
| ambiguity there and I beleive this code should be legal.

Since day ONE filePro has been case insensitive in-so-far as names of
dummy variables, labels, aliases and, later, long named variables.

The "withpod" label name and the "WithPOD" long variable neme therefore
are in conflict.

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).