Re: FreeBytes LIES - Memory leak in Director 8

[Kerry Thompson]

>>If you call a handler, be aware that Director will return to the next 
>>statement after the call when it's finished (the called handler, that is).
>
>This certainly is true.  But how does this have anything to do with any 
>potential "memory leak"?

Here's the scenario I ran into...

But bear in mind that it was back on my first Director project... John 
Sweeney is unlikely to make this sort of rookie error :-)

A sprite behavior calls a handler in a frame script.

The frame script goes to a label where the calling sprite doesn't exist.

When the stack unwinds back to the code in the original calling sprite, you 
get, um, unpredictable behavior. Like memory leaks.


Cordially,

Kerry Thompson


[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.  Thanks!]