Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Best Practices
Message
De
08/02/2013 09:25:32
 
 
À
08/02/2013 09:12:08
Mike Sue-Ping
Cambridge, Ontario, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01565478
Message ID:
01565479
Vues:
140
I used Set Procedure a lot earlier, but not anymore. I have only one procedure file active by Set Procedure To, if I need to add another one, I release it afterwards. I now always create separate prgs, or add the function to my functions.vcx.

I also avoid Set Classlib, instead I use NewObject() whenever possible. In Thor you will find a Dynamic Snippet called NO which I created roughly a year ago. When I need to use a class in a classlib, I only type "NO myclass" and press F5 which I have programmed to invoke the dynamic snippet. I then get a picklist of every class in my project where myclass is found, and end up with the working code.

>I'm working on an application that has many class libraries (VCXs) in the project. In the startup code, there is a SET CLASSLIB TO...ADDITIVE command for each and every VCX. The same goes for procedures; SET PROCEDURE TO ... ADDITIVE. Is there any drawback to doing it this way? I was wondering if there is any advantages of loading them on a "as needed" basis. Something along the lines of
>
>IF !"SOMECLASSLIB"$SET("Classlib")
> SET LIBRARY TO SOMECLASSLIB ADDITIVE
>ENDIF
>
>Then when its not needed, just RELEASE CLASSLIB SOMECLASSLIB. Would this be a more efficient use of RAM and/or does it affect the speed in any way?
>
>TIA,
>Mike
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform