Nicholas~
I will try to answer what I can, based on my current experience making those array PMCs.
Nicholas Clark wrote:
You are responsible for freeing it by setting the active destroy flag.a data pointer which I can use. I am always responsible for freeing anything there(?) and to do this I need to set the active destroy flag(?) This flag is not the same as the high priority DOD system(?) Does the garbage collector ever consider this pointer? Does it ever chase what it points to?
Well... no. You're not. If the memory hanging off the data pointer was allocated from one of parrot's managed pools (either free memory or pmc/buffer header) then you don't have to free it.
You only need to have a destroy function if you've malloc'd memory or need to actively tear down something, usually a filehandle or connection to a third-party extension or something.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
