Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Foxpro Life
Message
De
16/04/2017 08:20:48
 
 
À
16/04/2017 04:42:18
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:
01650264
Vues:
70
>>>
>>>Bottom line: IT IS INCREDIBLY HARD TO USE MDOT TO PROVIDE FULL PROTECTION AGAINST NAMING CONFLICT. If you control the database side of thing, IT IS SO EASY TO USE NAMING CONVENTIONS TO PROTECT AGAINST NAMING CONFLICTS
>>
>>What your examples demonstrate is that naming conventions are as hard to enforce as applying mdot on memory objects references.
>
>
>Please explain.. forcing naming conventions for fields are incredibly easy... For variables they are a lot harder... for applying mdot properly and consistently near impossible for mere mortals.

hdcCompat, hDC, and hbm use a different naming convention of lnWidth, and lnHeight.

Inconsistency is not a mdot intrinsic problem.
----------------------------------
António Tavares Lopes
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform