Re: usage of namespaces

[Magnus Norddahl]

Quoting Ingo Ruhnke (address@hidden):

> > The problem is when a libraries doesn't have its own namespace, so
> > some of the Pingus stuff can conflict with the library. Hm, but ok
> > then one could put the library into a namespace instead of the
> > application. Well, I never created namespaces myself so I don't really
> > know what I am doing.
> 
> And beside that a 'namespace Pingus' shouldn't make much difference,
> since everything in Pingus should be in namespace Pingus one wouldn't
> have to use tons of 'Pingus::' in the header files. In the .cc files
> one can use 'using namespace Pingus::...'

Yes well - its just that I've never really encountered such naming problems,
and even if you should encounter one, you'll just call your class something
slightly different. This is not possible for libraries, since they cannot
possible know what else the application is gonna use for class names, but
applications like Pingus, I just somehow find it bit overkill to put
everything into namespaces.

Anyways, just wanted to know your rationale behind using namespaces, which I
know now. :)

-- 
Magnus Norddahl,
Clansoft