Question

I just joined a new C++ software project and I’m trying to understand the design. The project makes frequent use of unnamed namespaces. For example, something like this may occur in a class definition file:

// newusertype.cc namespace {   const int SIZE_OF_ARRAY_X;   const int SIZE_OF_ARRAY_Y;   bool getState(userType*,otherUserType*); }  newusertype::newusertype(...) {... 

What are the design considerations that might cause one to use an unnamed namespace? What are the advantages and disadvantages?

Answer 1

Unnamed namespaces are a utility to make an identifier translation unit local. They behave as if you would choose a unique name per translation unit for a namespace:

namespace unique { /* empty */ } using namespace unique; namespace unique { /* namespace body. stuff in here */ } 

The extra step using the empty body is important, so you can already refer within the namespace body to identifiers like ::name that are defined in that namespace, since the using directive already took place.

This means you can have free functions called (for example) help that can exist in multiple translation units, and they won’t clash at link time. The effect is almost identical to using the static keyword used in C which you can put in in the declaration of identifiers. Unnamed namespaces are a superior alternative, being able to even make a type translation unit local.

namespace { int a1; } static int a2; 

Both a‘s are translation unit local and won’t clash at link time. But the difference is that the a1 in the anonymous namespace gets a unique name.

Read the excellent article at comeau-computing Why is an unnamed namespace used instead of static? (Archive.org mirror).