Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Commonly misused and abused VFP features
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00310951
Message ID:
00310954
Vues:
44
Jim, could you provide alternatives to these?

>Here's the beginning of a list of commonly misused and abused features, functions, and commadns fo VFP.
>
>1: Inheritence has to be the single most commonly misused feature of all OO languages.
>
>2: SET FILTER TO ... is very often used where another construct would do the job much more efficiently and with better performance.
>
>3: & the macro expansion feature is too often used where it is either not necessary or ther is a bettter way to accomplish the same goal.
>
>4: Filtered indexes, are often used where they are not necessary. The same result can be obtained using SQL without the overhead of having an extra index tag around all the time.
>
>5: UNIQUE indexes, not only are they misused but they could easily be totally removed from the product without any alteration in capabilities.
>
>6: PUBLIC variables are often used in situations where they are totally not required.
>
>7: SET EXACT is often used to cover for not understanding the way strings are compared in xBase. This causes the loss of a lot of functionality that is inherent in the product in order to adapt to a lack of knowledge.
>
>8: == is often NOT used where it should be. See SET EXACT above.
>
>9: Reports used for producing a screen display of readable data. Reports are for printing on paper, forms are for showing on screen. Report Preview is for eyeballing before committing to paper.
>
>10: PACK is too often sued in situations where any benefit it porovides is far outweighted by the costs associated with it.
>
>There's 10 of them, add to the list.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform