Sam Ruby <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> >> I think, when going down the class hierarchy, we just have to call >> class->vtable->find_method() again, istead of the Parrot_find_global.
> If "we" is Parrot_CompositeObject_find_method, then I'm quite OK with > that. If "we" is Parrot_default_find_method, then I'm fine too. > However, if "we" is src/object.c, then let's talk some more. The object's find_method vtable can do the method lookup on its own of course. The implementation in object.c should provide a reasonable default MRO. Composite objects that are ignoring the presence of foreign classes are not compliant to interoperbility. When the default method lookup calls again the find_method vtable of parents and this method continues method lookup in a compliant way, all should work. > Even if that were done, that would only handle cases where PyComplex > were the first argument. In general, it would be nice if there were a > way to express "for purposes of MMD this class is a Complex". Yep. > - Sam Ruby leo
