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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78367 --- shadow/78367 2006-05-12 06:00:06.000000000 -0400 +++ shadow/78367.tmp.18213 2006-05-12 07:01:09.000000000 -0400 @@ -122,6 +122,33 @@ * is there a chance that Microsoft will fix their compiler to disallow this code? * should we care? The standard's on our side + +------- Additional Comments From [EMAIL PROTECTED] 2006-05-12 07:01 ------- +Oops, yes. It was a duplicate of bug #75873. + +Now I re-read ECMA-334, and I noticed that there is a difference in +implicit conversion implementation for interfaces. It is denoted as: + +"From any interface-type S to any interface-type T, provided S is +derived from T." +http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csspec/html/vclrfcsharpspec_6_1_4.asp + +So, I think it is mcs bug. + +The following code demonstrates the same problem: + +-------- +using System; + +public class Tset +{ + ICloneable c; + IComparable b; + public bool Foo () { return b == c; } +} +-------- + +It compiles under MS.NET (1.1/2.0) and does not under Mono (mcs/gmcs). _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
