[Mono-bugs] [Bug 44845][Wis] Changed - MCS needs to flag an error when the same type is obtained from different assemblies

[bugzilla-daemon@bugzilla.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 miguel@ximian.com.

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

--- shadow/44845	2003-07-30 15:23:44.000000000 -0400
+++ shadow/44845.tmp.30083	2004-01-31 02:41:26.000000000 -0500
@@ -1,17 +1,17 @@
 Bug#: 44845
-Product: Mono/MCS
+Product: Mono/Compilers
 Version: unspecified
 OS: All
 OS Details: 
-Status: REOPENED   
+Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Wishlist
-Component: Misc
-AssignedTo: ravi@ximian.com                            
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: spouliot@videotron.ca               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: bmaurer@users.sf.net,lupus@ximian.com,miguel@ximian.com
 Summary: MCS needs to flag an error when the same type is obtained from different assemblies
@@ -257,6 +257,57 @@
 
 ------- Additional Comments From ravi@ximian.com  2003-07-30 15:23 -------
 CCing Miguel on this. I was pretty sure we had this capability inside
 MCS but I dont know why it isnt getting triggered.
 
 
+
+------- Additional Comments From miguel@ximian.com  2003-09-02 12:54 -------
+I have added the -d:INSIDE_CORLIB to the makefile profile, and this
+has fixed the compilation issue on Linux with the new makefile setup.
+
+
+------- Additional Comments From miguel@ximian.com  2003-11-27 01:07 -------
+Sample way to reproduce:
+
+File: 1.cs
+
+public class X {
+	public void P ()
+	{}
+}
+
+File: 2.cs
+public class X {
+	public void PP ()
+	{}
+}
+
+File: 3.cs
+class Y {
+	static X a;
+
+	static void Main ()
+	{
+		a.P ();
+	}
+}
+
+Compile like this:
+mcs -target:library 1.cs
+mcs -target:library 2.cs
+mcs 3.cs -r:1.dll -r:2.dll
+mcs 3.cs -r:2.dll -r:1.dll
+
+Notice the difference in output in the last two.
+
+------- Additional Comments From bmaurer@users.sf.net  2003-12-23 18:49 -------
+Created an attachment (id=6312)
+Patch
+
+
+------- Additional Comments From bmaurer@users.sf.net  2003-12-23 18:51 -------
+This patch makes us emit a warning, like MS does. However, a few problems:
+
+1) we do not get the location on the warning, this is pretty deep
+down, not sure how to get that
+2) will we create false warnings b/c we look up stuff internally?