[Mono-bugs] [Bug 69334][Maj] New - Class reference in another namespace compile error with "Type C is not found"

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

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

--- shadow/69334	2004-11-10 16:00:56.000000000 -0500
+++ shadow/69334.tmp.13170	2004-11-10 16:00:56.000000000 -0500
@@ -0,0 +1,48 @@
+Bug#: 69334
+Product: Mono: Compilers
+Version: 1.1
+OS: SUSE 9.1
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: naresh@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: edasque@ximian.com,james@ximian.com,tambet@ximian.com
+Summary: Class reference in another namespace compile error with "Type C is not found"
+
+(1) If a class is in namespace A.B.C and it tries to use a class called
+X.Y.C by saying "using X.Y" and referencing C directly in the code, then
+the code fails to compile with the message:
+  "Type C is not found".
+
+  This used to compile cleanly with Mono 1.0. So, I was wondering this
+was a bug with mcs.
+  A way to work-around to this bug is to write the code as "using C_new
+= X.Y.C;"
+
+>>> Miguel de Icaza <miguel@ximian.com> 11/10/2004 11:59:13 AM >>>
+Hello,
+
+> I wanted to pass this on, I'll have it Bugzilla'd shortly am also
+> checking with James on validity.
+
+This is two things:
+
+	* Fixing of the lookup rules (we had a broken implementation in
+	  1.0, and now we are closer to the C# spec).
+
+	* The error should have been `Ambiguous reference to class C',
+	  but a regression on the errors shows it as `Not found'.
+
+	  This has been fixed on CVS, and will ship on 1.1.3
+
+It is best to have bug reports filed on CVS though to make sure that
+issues are properly tracked.
+
+Miguel.