Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Memory Leaks
Message
De
23/07/2008 17:42:36
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
 
 
À
23/07/2008 17:31:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
Divers
Thread ID:
01333545
Message ID:
01333572
Vues:
12
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, '')
>>
>>
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform