Denis Shevchenko wrote:
12345678901234567890123456789012345678901234567890123456789012345
In addition, I think that a single standard of namespaces should be combined with a single standard of .hpp files location in main 'boost' directory.
+1
IMHO, simple libraries (such boost::mem_fn or boost::lexical_cast) which consist of a single .hpp file can (or must) be placed in main 'boost' directory, so user can write:
#include <boost/mem_fn.hpp>
-1 The single header libraries still have documentation and tests which should all fall into library-specific subdirectories of their respective parents. As noted elsewhere, boost/mem_fn.hpp can still exist, but it should simply include boost/<library>/mem_fn.hpp even though the latter may be the only header in boost/<library>. Not only does this follow a consistent pattern, but it also leaves room for later additions should they appear.
For more complex libraries, all .hpp files must be placed in own directory (like boost::ptr_container), so user writes:
#include <boost/ptr_container/ptr_container.hpp>
+1 Furthermore, the directory and namespace names should be identical. Thus, boost/ptr_container provides code in boost::ptr_container. _____ Rob Stewart robert.stewart@sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.