General information
Category:
Visual FoxPro Beta
Hi Thomas,
I'd say this *IS* a bug.
I can't say that I've ever seen this particular behaviour documented. The code definitely uses "m." to preclude other oddities (like field taking precedence).
I might expect differently with "PRIVATE" (have to think on that one) but here PUBLIC is declared.
All that said, I do get the same behaviour using VFP8 SP1 (I do not have VFP9 installed) so I quite possibly did miss/forget some prior words on the subject.
cheers
>Hi Fabio,
>
>this one is definitivelky not a bug. The behaviour is known since FPW,
>and I know I read about it in the docs then.
>I am fairly sure that the behaviour is still documented.
>A quirk of the language, but since it is documented, it shouldn't be called
>a bug. And I've come across quite a few apps which would break if this was changed:
>Consider programmers writing "half-generic" functions against global arrays
>and then exchanging help array's into the same name via calls by reference.
>
>Ugly as hell, but "running code".
>
>Regarding the previous one, call by ref with a table field:
>this is also the behaviour since very old days.
>
>Annoying, yes, but you could use it to find out if a
>table field exists ;-)
>
>regards
>
>thomas
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only