General information
Category:
Contracts, agreements and general business
>>>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
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