Dan Sugalski wrote:
I have, in the past, considered having a parent interpreter that doesn't ever run any code, and is around for the sole purpose of hanging 'global' parrot memory off of. I never did it because I wasn't sure we needed it, but it might be time to dust off the idea.
No more need for it. All PMCs/Buffers of the running interpreter are managed now. As for the interpreters structures itself - I'm almost finished with Parrot_destroy: I currently have _one_ memory leak WRT PIO - that's it.
leo
