Hi Linda,

Please pardon me for jumping in...

Isn't there a big BIG difference between a PROC and a class though?
- A PROC runs and is done; a class sticks around until released;
- A PROC runs and is done; there can be multiple classes in different 'states' active all at once.

It would seem that the memory consumed by classes or PROCs is likely small compared to memory consumed for table buffers and other I/O buffers.

2¢ CDN

JimN

>Hi Christof,
>
>Thanks for lowdown.
>
>>However, what VFP internally uses is a memory structure that is created the >first time a class is loaded and duplicated for each instantiated object.
>
>This is interesting because it implies that using OOP is more inefficient in terms of memory management than the old fashioned procedure files...If I create a custom object to store methods, it's really more inefficient than simply creating a procedure file and issuing a SET PROC TO...?! Unless SET PROC TO also loaded the whole proc file into memory, which doesn't seem logical, considering the limited memory of the older machines. Hmmm.
>
>Linda