On Sun, Nov 05, 2006 at 05:41:12PM +0100, Leopold Toetsch wrote:
Am Sonntag, 5. November 2006 15:22 schrieb Patrick R. Michaud:
So, I can create the missing cases, but what do I put for the body
of the method to get to the corresponding method of Capture?
.namespace [ 'Match' ]
Am Montag, 6. November 2006 21:54 schrieb Patrick R. Michaud:
Alas, this seems to work only for immediate subclasses of a PMC.
If we have a sub-subclass, then we're apparently back to the
same problem as before:
I somehow thought that any object subclass would have a proper object vtable,
but
On Sat, Nov 04, 2006 at 05:18:22PM +0100, Leopold Toetsch wrote:
Am Samstag, 4. November 2006 16:17 schrieb Patrick R. Michaud:
Because 'Match' doesn't define its own set_integer_keyed_int
vtable entry, it ought to be inheriting the one from Capture.
But unfortunately, the default.pmc
Am Samstag, 4. November 2006 16:17 schrieb Patrick R. Michaud:
Any thoughts about how we should resolve this?
This is fixed now with r15111.
Pm
leo
Am Sonntag, 5. November 2006 15:22 schrieb Patrick R. Michaud:
I don't think that's possible, is it? Match is implemented as a
subclass of Capture, as in:
$P0 = subclass 'Capture', 'Match'
So, I can create the missing cases, but what do I put for the body
of the method to get to the
Am Samstag, 4. November 2006 16:17 schrieb Patrick R. Michaud:
Because 'Match' doesn't define its own set_integer_keyed_int
vtable entry, it ought to be inheriting the one from Capture.
But unfortunately, the default.pmc function above gets in the
way, and redispatches the keyed_int call as a
Leopold Toetsch wrote:
Class inheritance from PMCs is very static still (like PMC-only cases). I hope
that the :vtable patches will provide the base for a better solution. For now,
you can only implement the mssing _integer_keyed cases in Match so that default
isn't triggered. We could of
On Fri, Nov 03, 2006 at 04:28:41PM -0800, Jonathan Worthington wrote:
Leopold Toetsch wrote:
Class inheritance from PMCs is very static still (like PMC-only cases). I
hope that the :vtable patches will provide the base for a better solution.
For now, you can only implement the mssing
Nicholas Clark wrote:
To me that feels like a hack. The current rather-too-static dispatch (to me)
seems to be the bug, and the thing that needs fixing.
Yeah, you're right. So, I decided to try and address this. From what I
can see, the problem comes up in building the v-table for the
