namespaces

[Magiaus]

I have to say that I love having access to namespace functionality, but am I the only one who has trouble deciding what to call them and how to structure them.

Like right now I am working with vc++.net to create an assembly to allow the creation of bots for diablo II in vb.net or c#. I am having trouble though well not with the code but with the namespace.

I can't deciede if I should use a one level name space such as Diablo or DiabloII or if I should go all out and be like Diablo.II.LOD then have all the methods and classes i am working on be under the LOD namespace until i deciede to add more for Diablo.I and for plain old Diablo.II. I dout i will ever write code for either...

So what do you guys think should i use one namespace or should I nest them and leave the first two namespaces empty. I am think I should nest them it makes more since that way to me at least...

[Cander]

I think you should name it Diablo.IILOD, because I doubt will be anymore expansions for it, so it is not necesssary having a thrird namespace level.

Now if there were maybe 3 or more expansions, then it would make more sense to make that thrid level (Diablo.II.LOD, Diablo.II.Expanson2, etc)