---- Reported by bmaurer@users.sf.net 2003-12-23 14:12:01 MST ----

namespace A {
	namespace B.C {
		public class D {
			public static void Main()
			{
			}
		}
	}
}

Should give
t.cs(2,12): error CS0134: Cannot use qualified namespace names in nested
        namespace declarations



---- Additional Comments From pcgod@gmx.net 2003-12-23 20:47:13 MST ----

Created an attachment (id=165384)
proposed patch




---- Additional Comments From bmaurer@users.sf.net 2003-12-23 21:15:26 MST ----

Created an attachment (id=165385)
Cleaner version




---- Additional Comments From bmaurer@users.sf.net 2003-12-23 21:16:16 MST ----

This version implements it in the parser, a cleaner impl IMHO. Most of
the credit goes to the other Ben.



---- Additional Comments From miguel@ximian.com 2003-12-25 17:17:32 MST ----

Am not sure if we should implement this, I remember seeing in the spec
it was allowed.  Can we double check?  (dont have the spec here).



---- Additional Comments From bmaurer@users.sf.net 2003-12-25 17:43:36 MST ----

csc will not compile it, so we should not. If we did, someone might
check something into cvs that would not compile on csc. It is clearly
not a bug in their impl, they went to the effort to create an error
message, reserve an error number, document the error number, etc. 

I can't find any spec references that explictly prohibit this
behavior, however nothing in the spec specifies this case. Can you
talk to the Microsoft guys about their rationale? I can't figure out
why they would reject such a decl.



---- Additional Comments From miguel@ximian.com 2004-04-11 00:43:16 MST ----

The construct is allowed in C# 2.0 (at least on MS VS.NET 2005 compiler)

Closing this

Imported an attachment (id=165384)
Imported an attachment (id=165385)

Unknown operating system unknown. Setting to default OS "Other".