Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro Life
Message
 
To
16/04/2017 10:39:02
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Contracts, agreements and general business
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Network:
Novell 6.x
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01649781
Message ID:
01650270
Views:
54
...
>>To summarize, what I get from the logic of your entire argument is similar to this: There are cars on the road with broken signal lights, or other drivers not using them, therefore it is useless to operate signal lights when driving. Using signal lights provides a false sense of safety.
>
>No its different. Lets say, if you're relying an self driving car to react primarily to the signal lights of the car in front of you, but not on the direction a car is going, you'll get the point.

Sure, drivers look around before changing direction (i.e. driving). Yet, everyone on the road is using signal lights, or at least they agree they're useful. I wonder why?

>>Bottom line: Use mdot, and the aliased variable is certain not to conflict with any field. Anything else is just dancing around the issue.
>
>It should be bottom line: AVOID VARIABLES AND FIELDNAMES TO BE THE SAME. If there is no choice then mdot is your only other option. And if you're fond of typing mdot, you might do it for additional safety. That is your choice.
>You are just like saying, if the car in front of you is not using its signal lights it won't turn to the left, but if the car in front of you has to avoid an obstacle, you'd better ignore the fact that he is not using its signal lights.


Like Dragan said, it is because of a bug that was advertised as a feature decades ago that now we have to deal with this. Other than that, of course, everyone tries to avoid the confusion of naming fields and vars the same. That's common sense, and not just in VFP. Unfortunately, the problem is that common sense (and your statement in caps above) may not, and sometimes it does not get you far enough. So, there is another option that would improve your chances, but you refuse to consider it because you claim it is not a perfect solution. So, I'll have to repeat again with complete certainty that
*
Using mdot will absolutely guarantee that the aliased variable will not create any conflicts, anywhere. It is a true, complete, independent, and simple statement, easy to follow. Do what you will with it.
*
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform