*) Inherited methods
*) Objects

The big issue with inherited methods is how we treat parents of PMC
classes, since they're both on a separate inheritance tree and also
feel like they've got a very different weight to them than standard
object-type inheritance. On the other hand, if we decide it isn't
really inheritance at all, rather just layered defaults, the problem
just goes away and that's fine too. Either way we need to build up
the tables so inherited MMD methods actually get inherited.

MMD for objects is a different thing entirely. Right now we have it
set up such that you *must* explicitly declare each MMD
method--there's nothing automatic (though there's a lot of
behind-the-scenes defaulting with PMCs) about how it works. Which is
fine, but if we do that we need to decide what level of HLL support
we want to give for getting MMD methods into the table in the first
place.

Other than that (and the first issue's been one all along) we're in
pretty good shape, and about where we were before we did the MMD
switchover.
--
                                         Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
d...@sidhe.org                         have teddy bears and even
                                       teddy bears get drunk