We don't call custom DESTROY methods if there are any (and there will be for quite a few things), and we don't call custom GC or mark-for-DOD routines, so if your PMC class has pointers to things in places Parrot can't get to by default they won't be copied properly or marked as used, respectively.
There's also an issue of when DESTROY can be called--since it's probably going to be perl code, we may not be able to just call it anywhere we want, since the interpreter may potentially be in an inconisistent st
Fantastic work! (Score:2)
Re:Fantastic work! (Score:2)
There's also an issue of when DESTROY can be called--since it's probably going to be perl code, we may not be able to just call it anywhere we want, since the interpreter may potentially be in an inconisistent st