I think this should generate a syntax error... whatdoeseveryone else think?

John Esak john at valar.com
Fri Jan 26 06:14:08 PST 2007


>
> > 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.
>
> There's nothing syntactically wrong with such an assignemnt.  You may
> argue that it's a semantic error that should be caught at runtime,
> but it's not considered an error.

> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>

It's not a very big deal to me at all... but would I really have to argue
the point? While it may not be an error, wouldn't it be helpful to the
filePro programmers to know that they have mistakenly assigned to a 0 length
field that can not possibly accept any data? So why would a warning when the
table is saved be beyond the many other ways you warn about other things
throughout filePro that are not really errors.

No need to answer this... just a comment. If I felt this was a serious
enough issue, I would send it to FP Tech as a wish list request. But, I
would hope that I could come up with at least 39 other things far more
important to put on that list before this.

John



More information about the Filepro-list mailing list