Organization of headers and their namespaces

Dear all, When using boost, there is one thing that annoys me. My editor can do syntax expansion quite well, but the amount of information in the boost namespace is so huge, that is really hard to locate anything, and near impossible to guess which classes and functions that belong to the same library. The obvious way to fix this to 1. let all libs have their own namespace, and 2. never let any library pull anything into namespace boost I think most recent libraries have adhered to 1., but possible not 2. My question is also if we, at some point, should start moving non-conforming libraries into their own namespace. This does break a library when upgrading, but might be worth it in the long run. Any thoughts? -Thorsten

On Jan 24, 2008 11:20 AM, Thorsten Ottosen <thorsten.ottosen@dezide.com> wrote:
My question is also if we, at some point, should start moving non-conforming libraries into their own namespace. This does break a library when upgrading, but might be worth it in the long run.
Not that I contribute code (yet), but it might be feasible to do one release where the new namespace is made available, but brought into the boost namespace for one release with a note saying that particular syntax is deprecated, then next release simply remove the using statement. --Michael Fawcett
participants (2)
-
Michael Fawcett
-
Thorsten Ottosen