Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory Leaks
Message
From
23/07/2008 18:19:29
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
 
To
23/07/2008 18:16:15
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01333545
Message ID:
01333580
Views:
11
Ok, are there other usual suspects for memory leaks? I've looked at dangling references and such, but don't see anything like that. Or that I can tell. I could suspend right after the process ends and before it begins again to see what is open, but what am I really looking for?

>No. The Return is not inside the WITH/ENDWITH. Your examples are fine. What is bad is:
>WITH oObject
>    RETURN RunSomething(.Child_001)
>ENDWITH
>
>
>>Do these scenarios cause problems? Or are we only talking about a RETURN in the same code block?
>>
>>
>>WITH oObject
>>     RunSomething(.Child_001)
>>ENDWITH
>>
>>WITH oObject
>>     NewChild = RunSomethingElse(.Child_002)
>>ENDWITH
>>
>>
>>PROCEDURE RunSomething
>>
>>     PARAMETER tChild
>>
>>     Do something with tChild
>>
>>     RETURN
>>
>>
>>PROCEDURE RunSomething
>>
>>     PARAMETER tChild
>>
>>     Do something with tChild
>>
>>     RETURN tChild
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform