On Fri, May 29, 2009 at 7:53 AM, Stewart, Robert <Robert.Stewart@sig.com> wrote:
JOAQUIN M. LOPEZ MUÑOZ wrote ...
Of course we have to leave the current headers there for compatibiltiy, but that location could be deprecated and eventually only <boost/filesystem/filesystem.hpp> supported.
*This* is less attractive to me; I think a Boost lib is entitled to have at least one top level header; many use it to include all or the the most usual components.
There's no entitlement involved. Leaving such files in the root directory dissociates them from the rest of the library which mitigates against modularization, which is a laudable goal.
I agree. Allowing headers in the top level just doesn't scale. That appears to be true regardless of the particular header modularization approach taken. --Beman