Johannes wrote:

some time ago I already reported a compilation problem that currently only exists on DragonFlyBSD. The namespace "signal" in the lout library collides with a function declaration in /usr/include/signal.h. For some reason DragonFly happens to include signal.h indirectly. But the same problem will appear on Linux too once we should need signal.h somewhere. Just try to compile the following C++ file (g++ -c <file>):

#include <signal.h> namespace signal { }

I'd like to resolve this issue before release. I see two options:

* rename namespace "signal" to "loutsignal" - which is pretty ugly. The concept of namespaces exists to avoid such stuff...

* put all classes in the lout directory into a single namespace "lout".

At the moment I prefer the second option, but I don't know Sebastian's reasoning behind this naming.

Any opinions?

I agree with you.