Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory Leaks
Message
From
23/07/2008 17:42:36
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
 
To
23/07/2008 17:31:39
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01333545
Message ID:
01333572
Views:
11
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
>Any return inside a WITH/ENDWITH. Doug Hennig blogged about it a couple of years ago. http://doughennig.blogspot.com/2006/04/dont-return-inside-with.html
>
>He says it causes C5, but is a memory leak.
>
>>No memo fields and we can watch the used memory grow as it is running. I asked in the other thread, but why is the RETURN a bad thing in the WITH/ENDWITH?
>>
>>Update: And does that mean any type of RETURN, like this?
>>
>>
>>RETURN CHRTRAN( InputText, CharsToStrip, '')
>>
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform