[Mono-bugs] [Bug 21554] Changed - Not correct overloading resolution

[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 f_ai@hotmail.com.

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

--- shadow/21554	Fri Mar  8 11:40:10 2002
+++ shadow/21554.tmp.22454	Fri Mar  8 15:38:01 2002
@@ -1,14 +1,14 @@
 Bug#: 21554
 Product: Mono/MCS
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: f_ai@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -49,6 +49,25 @@
 				return true;
 			
 			return false;
 		}
 	}
 }
+
+------- Additional Comments From f_ai@hotmail.com  2002-03-08 15:38 -------
+The fix for the problem is not really as simple as i suggested 
+before, the provided source code will compile (after the call 
+change) but the problem is far from over.
+
+In this case it works because the the method 'N' has only one 
+implementation with only one parameter, so it really works as a side 
+effect.
+
+Here are some more details:
+On the OverloadResolve, when we get to the part where we have no 
+BEST yet, and we start to consider all the methods with the same 
+number of arguments as the target, all the methods that have the 
+same number of arguments are treated the same, and the last one is 
+the one that is defined as the BEST. Probably the BetterFunction 
+must be called to choose the best function.
+The BetterFunction should probably be changed, to include the 
+UserInplicitConversions information for the parameters if any.