I have read Uncle Bob's Clean Code a few months ago, and it has had a profound impact on the way I write code.  Even if it   seemed like he was repeating things that every programmer should know, putting them all together and putting them into practice does result in much cleaner code.  In particular, I found breaking up large functions into many tiny functions, and breaking up large classes into many tiny classes to be incredibly useful.  Now for the question.  The book's examples are all in Java, while I have been working in C++ for the past several years.  How would the ideas in Clean Code extend to the use of namespaces, which do not exist in Java?  (Yes, I know about the Java packages, but it is not really the same.)Does it make sense to apply the idea of creating many tiny entities, each with a clearly define responsibility, to namespaces?  Should a small group of related classes always be wrapped in a namespace?  Is this the way to manage the complexity of having lots of tiny classes, or would the cost of managing lots of namespaces be prohibitive?Edit: My question is answered in this Wikipedia entry about Package Principles.
Best practices for using namespaces in C++
design;c++;namespace