If I didn't have to store the references to Temps, it's well known that any Temps objects will be destroyed once they go out of scope, but that won't happen in this case. While Temps is small and should not drastically exhaust resources in terms of memory even if thousands are defined, I'd still rather avoid this situation, if not for this particular problem but for future situations of a smilar nature.
As it is right now, I'm providing a function to the end user that allows them to manually clear out the Temps. Icky, I know, but it does allow the end user that might be concered about memory usage to do something about it. If I can resolve this problem now, then I'll since drop this function to a 'do nothing' state for compatibility.
Is there a way to capture the point where an object is going out of scope but not necessarily being deleted, such that special actions can be taken?
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important
In reply to Catching an object going out of scope by Masem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |