Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
M. performance
Message
 
 
À
25/04/2002 17:05:21
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., Nouvelle Zélande
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Divers
Thread ID:
00647967
Message ID:
00649428
Vues:
26
Hi John,

I believe, this question should be asked to MS team and not to me. Cetin found this difference, I personally use m. where applicable (Mike Y rule), but none of my colleagues uses this notation (except for one, whos style I liked and adopted).

We're still working in VFP6 to my regret. I raised the question about "When we'll switch" few times, but didn't receive an answer yet...
My workstation is Windows 95 and we have in the office only Windows 95 and Windows 98...

>Nadya
>
>If VFP7 now provides a significant performance benefit for using m. on the right side of variable assignments, I'd have to ask WHY. How does that help us?
>
>With VFP3 and the need to rewrite lots of our work, many of us *deliberately* moved from m. to Hungarian notation for reasons well described elsewhere. Prior to that, we only had 10 character field labels and it was rare to see variable or field "type" implicit in field or variable labels. In addition it was normal to use scatter/gather in entry forms to mimic optimistic buffering at a time when pessimistic was the only option. So m. was routine to avoid error.
>
>The change to Hungarian aided maintenance hugely IMHO. The use of an initial l for locals did away with possible field/variable contention. I was comforted by regular newsgroup postings suggesting that this was faster than m. anyway.
>
>I do not want to revert to m. and would like to know what VFP7 improvement has taken place with the unfortunate side effect described!
>
>Regards
>
>JR
If it's not broken, fix it until it is.


My Blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform