I think this should generate a syntax error... what
doeseveryone else think?
John Esak
john at valar.com
Thu Jan 25 19:08:39 PST 2007
>
> Quoting John Esak (Thu, 25 Jan 2007 18:41:26 -0500):
> [...]
> > I had mistenly type in a huge series of lines...
> >
> > if: 109 eq "0"
> > then: 009=""
> >
> > Of course, I meant it to be 109. No syntax error... I've been running
>
> Leading zeros in numbers aren't significant. Therefore, the numbers
> "009" and "9" are equivalent.
>
Yes, but we are talking about *fields* here... what if I were trying to
assign to 00a... wouldn't you throw up an error? I know you say leading
zeros on numbers... but... but...
> [...]
> > Also, while we are at it. I just tried assigning to field 229 when it
> > doesn't exist. No error, no warning. I think this would be helpful to...
>
> I get a syntax error.
>
> [...]
>
> --
> KenBrody at BestWeb dot ne
Okay, I know why you did get an error and I didn't. Try this.
Define a file with 9 10 character fields in it. Then assigning to any field
up to 9 works fine and anythign above 9 gives the syntax erro. Now, go back
into the file and hold the SPACE bar down starting at field 7 so that you
completely erase everything in the field descriptin, length and edit type
for rields 7 through 9. Save the able.
Then, when you assign to field 9, which you *know* you just removed, it does
not complain in any way. No syntax error. Yes, I see thatthe fields are
still actually there with the colons and all in the map... and they are
visible on the F6 screen... it just seems odd that the fields can be
completely empty and still be able to (or at least *appear* to be able to)
take assignment.
My bad.
John
P.S. God, did I actually use the terminolgy "My bad"? It is now officially
time for me to kill myself. Good by cruel world.
More information about the Filepro-list
mailing list