Am Wednesday 28 October 2009 18:44:30 schrieb David Abrahams:
Works for MPL. Nobody ever wonders where to find anything in MPL.
...
I don't care (very much) which convention we choose, but I would very much prefer, for our users' sake, to choose one uniform #include convention that works for all the libraries.
from the users perspective alone, you'd expect directories to match namespaces and filenames.hpp to match classes (or something that identifies > 1 classes). i.e. boost::mpl::and is in boost/mpl/and.hpp this would overcrowd some directories, especially boost/*, but since identifiers in namespace boost are already unique that isn't a problem from the user's perspective. it might create all sorts of maintenance issues though, having files from dozends of different boost libraries in the same directory.