Good Namespace Naming Conventions

Question

I am creating a class library for a CRUD business application. The major \"categories\" of business objects (with related data access layer objects) are:

• Maint

Answer 1

I use one namespace per library and one per executable source code set. The names are always short. For example, in the executable I'm currently working on, I have:

• ALib - my general utility library
• Mongo - my mini web server library
• DBLite - my SQLite3 wrapper & simple persistence layer
• Track1 - executable (actually a couple of executables)

This seems to work pretty well. I find that very complex namespace schemes should be avoided, in the same way that very complex, deep class heirarchies should.