[Mono-bugs] [Bug 74996][Blo] Changed - MI/ method lookup oddness ...

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lluis at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74996

--- shadow/74996	2005-05-27 09:34:47.000000000 -0400
+++ shadow/74996.tmp.575	2005-05-31 07:45:39.000000000 -0400
@@ -332,6 +332,21 @@
 hence trampoline generation for me quite nicely :-)
 
 I guess it could be substantially more optimal; it's also the case
 that the if (*count < 2 ) thing is a bug - 1 interface can still be
 missing an arbitrarily large number of derived sub-interfaces ;-)
 should improve that check I guess.
+
+------- Additional Comments From lluis at ximian.com  2005-05-31 07:45 -------
+I think that mono_class_proxy_vtable should recursively add slots for
+indirectly inherited interfaces into the vtable. I don't think this is
+a metadata issue.
+
+Mono doesn't seem to have any problem dealing with the XMulti
+interface, which does not explicitely defines the inherited
+interfaces. I can create a class that implements XMulti and it works,
+and typeof(XMulti).GetInterfaces() returns all inherited interfaces.
+
+I've been able to reproduce the bug in mono by implementing an
+interface hierarchy in IL, and using it from a c# app.
+
+I'm taking a look at this.