Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Foxpro Life
Message
De
17/04/2017 16:37:10
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., Nouvelle Zélande
 
 
À
14/04/2017 17:55:25
Walter Meester
HoogkarspelPays-Bas
Information générale
Forum:
Visual FoxPro
Catégorie:
Contrats & ententes
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Network:
Novell 6.x
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01649781
Message ID:
01650304
Vues:
82
>>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...
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform