Mike Sue-Ping
Cambridge, Ontario, Canada
>>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.
>
>Yes, I've found NEWOBJECT is a LOT slower. If it's in a loop, or needs to be called from any of they Dynamic* stuff in a grid you'll want to stay away from it.
Thanks. Good to know this cause I actually have code calling newobject in a small scan loop. Currently I don't have any issues with it, however, I'm curious to know if changing it will get better performance.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only