I
Ivor Somerset
Hello,
In my ASP code I sometimes write functions that return an object
(generally an XML node).
Such a function is invoked this way:
Set Object1 = MyFunction(SomeValue)
And at the end of the process the object will be properly destroyed:
Set Object1 = Nothing
Now, in the function body, an object is instantiated that bears the name
of the function:
Function MyFunction(SomeArgument)
Set MyFunction = (...)
End Function
My question is: what about memory, given that the object instantiated in
the function *cannot be set to nothing* (no object would ever be
returned to the main process)? Does ASP have some garbage collector that
deals with this situation?
Thanks in advance for your answer.
Ivor
In my ASP code I sometimes write functions that return an object
(generally an XML node).
Such a function is invoked this way:
Set Object1 = MyFunction(SomeValue)
And at the end of the process the object will be properly destroyed:
Set Object1 = Nothing
Now, in the function body, an object is instantiated that bears the name
of the function:
Function MyFunction(SomeArgument)
Set MyFunction = (...)
End Function
My question is: what about memory, given that the object instantiated in
the function *cannot be set to nothing* (no object would ever be
returned to the main process)? Does ASP have some garbage collector that
deals with this situation?
Thanks in advance for your answer.
Ivor