[Mono-bugs] [Bug 30606][Nor] Changed - mcs report errors when formal parameter is an interface and actual parameter is object that implements the interface

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
25 Sep 2002 21:00:12 -0000

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.


--- shadow/30606	Thu Sep 19 17:49:17 2002
+++ shadow/30606.tmp.22533	Wed Sep 25 17:00:12 2002
@@ -1,12 +1,12 @@
 Bug#: 30606
 Product: Mono/MCS
 Version: unspecified
 OS: unknown
 OS Details: SuSE Linux 8.0
-Status: NEW   
+Status: NEEDINFO   
 Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: mathpup@mylinuxisp.com               
@@ -64,6 +64,17 @@
 ------- Additional Comments From gonzalo@ximian.com  2002-09-19 03:03 -------
 It seems that Type.IsAssignable from is the answer...
 ------- Additional Comments From martin@gnome.org  2002-09-19 17:49 -------
 So you think this is a runtime bug ?
+------- Additional Comments From miguel@ximian.com  2002-09-25 17:00 -------
+This works for me on my copy of MCS from CVS.  Which version are you
+We also only use Type.IsAssignableFrom in two places: one to test for
+delegates and one for foreach statements (where it is pretty easy to
+control the scope, as IsAssignableFrom has not the semantics the
+compiler needs everywhere else).
+So, no, it is not a runtime bug (if it is a bug)