[Mono-bugs] [Bug 44845][Wis] Changed - MCS doesn't find the best overloaded match for a constructor

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Mon, 23 Jun 2003 12:24:53 -0400 (EDT)

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 lupus@ximian.com.


--- shadow/44845	Fri Jun 20 20:00:33 2003
+++ shadow/44845.tmp.32704	Mon Jun 23 12:24:53 2003
@@ -123,6 +123,23 @@
 pointers are not the same so we have :
 Mono.Security.X509.X509Extension -> Mono.Security.X509.X509Extension ?
 0x819b7f0 -> 0x81f8b08
 Any ideas, Lupus ?
+------- Additional Comments From lupus@ximian.com  2003-06-23 12:24 -------
+The pointer comparison is right.
+The issue here is probably that mcs finds
+Mono.Security.X509.X509Extension both in corlib and in the
+Mono.Security assembly (Mono.Security is compiled inside corlib, AFAIK).
+Since the types come from different assemblies, they are different,
+even if the name and the implementations are the same: my guess is
+that mcs picks the type from one assembly in one case and from the
+other one in another, but since they are not the same types, the
+method signatures don't match. To sum it up, there are two issues:
+*) the types of the assemblies included inside corlib need to be
+marked internal, since they must not be exposed (we need a define for
+*) there is a mcs bug: it should flag it as an error when it finds
+that the same type is available from more than one assembly.