#528: Clone and Modify in DynPMC VTABLE Initialization
-----------------------+----------------------------------------------------
Reporter: chromatic | Owner: chromatic
Type: roadmap | Status: assigned
Priority: normal | Milestone: 1.2
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Comment(by cotto):
Replying to [ticket:528 chromatic]:
> We need a way to map the appropriate slot in the vtable array for each
overridden entry. That's easy. We need a way for a dynpmc to access and
clone its parent's vtable. That's a little bit more work, if only because
we have to do this in generated code, and it's a divergence between how
dynpmcs initialize their vtables and how built-in PMCs initialize their
vtables.
Why does there need to be a divergence? It sounds like this approach
would work just fine for built-in PMCs too, if perhaps with a slightly
higher runtime cost.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/528#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
