chromatic (via RT) wrote:
However, it does mean that if we keep up this line of thinking, we do need a way to identify ParrotIOLayers that hold PObj pointers and mark those pointers during DOD.
ParrotIOLayers are going away, to be replaced by a class and C-level roles. It does bring up a good point that C-level roles will need a way to modify the 'mark' vtable function of the composed class. We can probably make this part of the ATTR syntax for defining the attributes of the class/role. Either all PMC attributes are marked by default, or we add a MARK keyword to specify when an attribute should be marked. Or, they're marked by default and not marked when specified as NOMARK.
Allison
