Thanks tony.
Nice example :-)
Seems that it does get Deleted at some point, which is just what you want.
As for *when* it happens. I'm not too concerned. It'll be up to the user of the Type to release it when they are done (and call gccollect if they want it sooner) with it anyway, after which it looks like I can rely on Max calling the Objects Delete() method - and subsequently allowing the object to free the memory it allocated.
I'm usually not one to use MemAlloc/MemFree/etc, but I'm finding it easier than having to do more code in C.
Thanks for the info, everyone :-)
Nice example :-)
Seems that it does get Deleted at some point, which is just what you want.
As for *when* it happens. I'm not too concerned. It'll be up to the user of the Type to release it when they are done (and call gccollect if they want it sooner) with it anyway, after which it looks like I can rely on Max calling the Objects Delete() method - and subsequently allowing the object to free the memory it allocated.
I'm usually not one to use MemAlloc/MemFree/etc, but I'm finding it easier than having to do more code in C.
Thanks for the info, everyone :-)