[Mono-bugs] [Bug 26204][Nor] Changed - Problem when finding an inherited method

[bugzilla-daemon@rocky.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 miguel@ximian.com.

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

--- shadow/26204	Mon Jun 17 04:23:05 2002
+++ shadow/26204.tmp.1404	Tue Jun 18 17:06:41 2002
@@ -84,6 +84,37 @@
 yourself?
 Anyway, once that is done (and I fix the code in our reflection to
 take into account the different DeclaringType and ReflectedType) I'll
 be able to emit in the binary image the correct memberref. It still
 won't work with the ms runtime: we need to file a bug with them about
 the issue.
+
+------- Additional Comments From miguel@ximian.com  2002-06-18 17:06 -------
+Well, DeclaredOnly is used in the MemberLookup routine, and the
+reason I need to use DeclareOnly is look things up in the order they
+will show up in the type hierarchy (beginning at the bottom).
+
+Ie: if you have a field in a base class, and a method in a later
+class, I would not get the right field.  That is why I "walk" things
+with DeclaredOnly.
+
+Ie, at that point, I do not *know* what I am looking for: I am just
+doing a name lookup (later stages will choose what exactly I am
+looking for).
+
+I wonder if I could just look things up, and if I find a method match,
+then re-run the FindMembers on the queried_type for the method.
+
+Not quite sure if this will work.  What will happen if I have:
+
+class X {
+    public void A ();
+}
+
+class Y : X {
+    public void A (int a);
+}
+
+I can do this in the last chunk of the routine `tUrn this into a
+method scan mode'.
+
+