Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The object itself
Message
From
28/05/2007 22:33:41
 
 
To
28/05/2007 16:13:27
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Object Oriented Programming
Environment versions
Visual FoxPro:
VFP 6 SP5
Miscellaneous
Thread ID:
01228871
Message ID:
01228960
Views:
21
>>Beware with this method since I doubt that the GC of VFP will clean up the class when it is released because of the circular reference. I've done a quick test and you can see that the memory is not released.
>
>I've tried to add
>
>this.self=null
>
>in the .destroy() of the class, but the consumption remains the same. Doing a Set Procedure, then later Release Procedure also did not help.

No, you need to put 'This.Self=null' in the Release(), and then you need to release the object - abc.Release() instead of (or after) abc = null. Of course this means you always need to release the object explicitly. Letting it go out of scope won't do the trick.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform