Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Foxpro Life
Message
De
12/04/2017 13:30:27
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
12/04/2017 08:43:54
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
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:
01650104
Vues:
56
>In my foxpro life I have run into many mdot discussions and even was challenged in one way or the other. I supplied numerous codes that demonstrate the need to use mdot. None of the ones who object to using mdot could provide a single -just one single- code piece that shows using mdot is harmful in any way. The only funny objection is "readability" and typing 2 extra characters - actually using mdot not only increase the readability but also provides intellisense support :)

The one place where I frequently use mdot is the command window. My short term memory is very accentuated, on the word "short", and it's getting more so as the year counter ++es. So when I'm sitting on the debugger and want to see the value of a variable or, more frequently, the properties of an unknown object, by the time I get to the command window I will forget its name. So I type the mdot and it all comes back to me :).

Inside the code, however, mdot doesn't bring up intellisense for me (maybe I miss a setting) but I have one of Thor's aides on a hotkey (alt+V for variable). And all the field names have 4 char prefixes (actually 3 plus underscore).

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform