Do not name a class the same as its namespace, Part Four

re: Do not name a class the same as its namespace, Part Four

Stephen — Tue, 24 Apr 2012 18:57:49 GMT

This does make it hard when you want namespaces like this:

Doctor.Events, Doctor.Services, Doctor.BusinessObjects

And then in Doctor.BusinessObjects you want a class called Doctor.

Each namespace is a type of Doctor functionality, but you can't call them that and still have a Doctor class.

re: Do not name a class the same as its namespace, Part Four

Newell Henry Clark — Mon, 09 Jan 2012 22:27:36 GMT

Thanks, man. I just went and renamed my static GameEngine class to GameEngineUpdator. It was originally NewellHenryClark.GameEngine.GameEngine, but now I know better, all thanks to you :D

re: Do not name a class the same as its namespace, Part Four

Alex — Thu, 01 Apr 2010 20:02:53 GMT

The Los Angeles Angels ought to play nothing but doubleheaders.

re: Do not name a class the same as its namespace, Part Four

Julien Lebosquain — Wed, 24 Mar 2010 07:59:43 GMT

Is there any reason why System.Configuration.Configuration doesn't follow this rule? It's always painful to use in code. System.Configuration.Config (or something similar) would have been much better, like there isn't a System.Text.Regex.Regex for instance.

My guess -- and I emphasize that this is a guess -- is that the class in question was invented *before* the framework design guidelines were written. -- Eric

re: Do not name a class the same as its namespace, Part Four

Szindbad — Mon, 22 Mar 2010 16:07:49 GMT

John: I like this feature because the folder structure and namespaces are two independent hierarchies, but this feature is try to make them similar, which is beneficial for project "complexity". Managing one hierarchy instead of two is huge benefit.

re: Do not name a class the same as its namespace, Part Four

John — Mon, 22 Mar 2010 12:37:46 GMT

One of the annoying (to me that is) characteristics of VSxxxx is that when you add a folder in a project, Visual Studio defaults classes in the folder to a namespace which ends with the name of the folder. If a programmer is using the folders for physical (as opposed to namespace) organizational purposes, she/he either has to remove the folder name from the namespace of the new class or add a new using statement to include that folder. In tools/options, the programmer should be able to limit the default namespace to the project.

re: Do not name a class the same as its namespace, Part Four

Gabe — Fri, 19 Mar 2010 22:18:19 GMT

I was just wondering what happens to a class when you declare it without a surrounding namespace{}. It appears the answer is that it goes in the implicit global namespace.

The first C# app I wrote was for .Net 1.1, and I forgot to put one of my classes in a namespace declaration. Well, it just so happened that when .Net 2.0 came out, it declared a class by the same name. When somebody ran my app on a computer with .Net 2.0 installed but not 1.1, it ran in the 2.0 CLR and got the new class of the same name.

re: Do not name a class the same as its namespace, Part Four

Stuart — Fri, 19 Mar 2010 20:37:02 GMT

oh no it doesn't compile, needs a "return" in there. Drat.

re: Do not name a class the same as its namespace, Part Four

Stuart — Fri, 19 Mar 2010 20:29:45 GMT

namespace Buffalo {

public class Buffalo {

Buffalo.Buffalo buffalo(Buffalo.Buffalo Buffalo) { buffalo(Buffalo); }

}

I think that actually ought to compile, although I haven't tried it. Infinite recursion when run, however.

re: Do not name a class the same as its namespace, Part Four

Stuart — Fri, 19 Mar 2010 20:27:09 GMT

Obligatory mention of buffalo.