#185: thawed subs with :vtable don't register properly for existing classes
----------------------+-----------------------------------------------------
Reporter: jhorwitz | Owner: jhorwitz
Type: bug | Status: assigned
Priority: normal | Milestone:
Component: core | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Changes (by jhorwitz):
* owner: => jhorwitz
* status: new => assigned
Comment:
The attached patch fixes the problem and all tests pass, but I'd like a
review just in case there are unintended consequences.
The patch checks for a sub's vtable_index and, where appropriate, uses the
vtable method's name in lieu of the sub's name. I had to add one
additional function, Parrot_get_vtable_name, so I could reliably map the
vtable index to the method name (various preprocessor directives prevented
me from accessing it from PMC code, and this seemed cleaner anyway).
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/185#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
