[Mono-bugs] [Bug 52586][Wis] Changed - We do not handle overriden overloads correctly

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 4 Jan 2004 12:28:44 -0500 (EST)

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 bmaurer@users.sf.net.


--- shadow/52586	2004-01-04 12:03:50.000000000 -0500
+++ shadow/52586.tmp.29409	2004-01-04 12:28:44.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 52586
 Product: Mono/Compilers
 Version: unspecified
+OS: unknown
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Wishlist
 Component: C#
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: bmaurer@users.sf.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -62,6 +62,18 @@
 As such, when we do overload resolve, we follow the clause:
 `6  If N is applicable with respect to A (, then all methods
 declared in a base type of T are removed from the set.'
 Thus, the int overload is incorrectly removed from the applicable members list.
+------- Additional Comments From bmaurer@users.sf.net  2004-01-04 12:28 -------
+This is pretty dificult, for inside the assembly, we can just not add
+the MethodInfos if they are override (easy)
+However, for other assemblies, we cant do that because of the way do
+method lookups. That second cache that we have will give the method
+with a DeclaringType which is wrong.
+Miguel -- what is the reasoning behind the MemberCache using the
+special hashtable for methods in external assemblies? The comments say
+you need the correct ReflectedType, why is the correct type needed?