Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Destroy method of biz object is not fired when it's real
Message
 
 
To
22/02/2005 11:01:16
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Miscellaneous
Thread ID:
00989209
Message ID:
00989807
Views:
29
>This is what I used to test, and it confirms your observations.
>
>DO STARTMM
>DEFINE CLASS Test as kbizness of kbizness.vcx
>   PROCEDURE Destroy
>      Debugout This.Name+".Destroy()"
>      DODEFAULT()
>   ENDPROC
>
>DO Test1
>DO Test2
>
>PROCEDURE Test1
>   LOCAL oTest
>   oTest = CREATEOBJECT("Test")
>   oTest.Release()
>PROCEDURE Test2
>   LOCAL oTest
>   oTest = CREATEOBJECT("Test")
>
Chris,

What do you think we should do about it? I was working on something else this morning but now I have some time, so I may try to find the offender. But the question is: how can I find the objects which are still in memory? And how can I test memory before instantiating the object and after that?

Thanks.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform