Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best Practices
Message
From
08/02/2013 10:00:11
 
 
To
08/02/2013 09:52:59
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01565478
Message ID:
01565491
Views:
102
I saw some benchmarks and newobject() was slower by quit a bit.
But as vfp is nota language to be used with throwaway classes and objects like dotnet and java,
that difference should still be minimal - as long as forms are still read as complete vcx and not built in code.

But if objects are created in a tight loop, I'd stay away from newobject().

>Instanciating a class will always use memory. How come NEWOBJECT () is different ?
>
>>It will take more time to newobject() because memory has to be allocated. However, as fast as computers are today, I don't think you'll notice the difference.
>>
>>You could also go a hybrid route and use a class factory. The class factory would load the classlib or procedure as needed, then just keep a reference to it. That way, things are only loaded if needed, but kept after that.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform