Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG: return a new object by reference fire a C5 crash
Message
From
13/04/2004 12:15:19
 
 
To
13/04/2004 12:11:38
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00893984
Message ID:
00894460
Views:
13
Hi Bob,

The reason you should always use m. prefix is that if you have an open table selected, and a field has the same name as a variable, VFP will ALWAYS refer to the field UNLESS you use m. And m. is a little bit faster.

>
>Yes, but the bug is not correlate with the reference parameters.
>I can reproduce it without parameters.
>
>Another workaround is:
>
>STORE m.This TO m.oObjectRef.myReference
>

>
>But when you reproduce it with out the m.THIS rather use just THIS does it still exist?
>
>BTW, is there a reason you (and other people) preface memory variables with "m."? I know back in the day it was either required or suggested but it seems to cause more problems then it's worth which is nothing. In my testing there aren't any performance benefits so what's the point? Just courious.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform