<snip>

>>Honestly, to optimize VFP is not simple,
>yes and no: I usually optimize at the application level, where most of the runtime is spent by mistakenly employed vfp - checking rushmore's pro and con's, possible system bottlenecks and hardware/os settings are often enough. Still, the exact code positions have to be isolated...
>
>Sometimes I add a few new patterns - in case of object creation/destruction for instance I replaced on the fly created message/parameter objects in a n-tier framework solution (up to more than a hundred con/destructs between user interaction, but run when already a nontrivial number of objects are instantiated) to using persistent object stacks, eliminiating most of the overhead.
>
>What kind of applications do you work on that need this finegrained control or have to be optimized on that level ?
>
>regards
>
>thomas

Mine it is a general speech.

I'm not sure to have understood.
However, I have developed a CASE for to support my developer job, and on it the objects they are constructed "on demand"
(today I have not add a Timeout Timer to release old unused objects, but this is not hard and when
the relase time grown a lot a add this sure)
But, Thomas, known you ( or some other reader ) thie answer ?

If ( like example ),
running an application, the app use 100000 Classes ( not objects !!! classes ),
but medium they are in use 1000 classes only ( for to maintain on live 5000 objects ),
the VFP's VM maintain in memory all the 100000 classes and therefore must make I a CLEAR CLASS,
or the VM manage this automatically ( and then a Class can to be reloaded at a not deterministic time )?
The two things are MUCH different one, and this conditions the way to construct the classes correctly.

I Hope that you can understand this english.

Fabio