Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro Life
Message
 
To
17/04/2017 16:37:10
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
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:
01650305
Views:
64
>>>Agreed to disagree, but bear in mind that your reference to me and my view on the matter in the prior messages was not what I expected from you either. Hence my question whether it was really you.
>
>Is it important enough to dispute?
>
>I use Mdot by habit as well as HN and sometimes scattered objects or even scattered local memvars for quick munging, so there's no mutual exclusion. However, there is a definite effect of "not using variable names that match fields" wrt VFP Compiler. The compiler pulls the field names for all tables or views used in your code, and doesn't mess with variables named same as a field, or that are used in macro substitution, or a few other circumstances where obfuscated variable names might cause a SNAFU. So your convention delivers better obfuscation. Not that everybody cares about that...

I was wondering about that. It is obvious why Chen had to work around the ambiguities, but wouldn't you think that mdot would make an obfuscator's job so much easier when it comes to variables? In other words, there would be no ambiguity on that mdotted token.
*
Previous
Reply
Map
View

Click here to load this message in the networking platform