Re: [boost] namespace boost?

Subject: Re: [boost] namespace boost?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-01-18 13:26:21

Steven Watanabe wrote:
>
> How about we just say that a library should reserve
> a single name under boost and how it uses it is up
> to the library author (i.e. a single header, a directory,
> or a directory + header are all fine.).  If we're
> just trying to keep the top-level boost from getting
> cluttered, there's no reason to overspecify the
> solution.

I don't think encouraging that the top-level header do nothing but forward to a header in the library directory is overspecifying.  Within this thread there was mention of forgetting to update the top-level header to match changes in the library directory.  If it only forwards to a single header in the library directory, then all places to make changes are within the library's directory.

Beyond that, they way you've described it captures the idea pretty well.  The all.hpp discussion was, really, as a replacement for top-level headers.  However, it wouldn't hurt to suggest that the top-level header might include boost/library_name/all.hpp as a guide to new library authors to remove the need to invent something for each new library.  (By making it a suggestion, most will follow the convention, but choosing another filename would not be wrong.)

_____
Rob Stewart                           robert.stewart_at_[hidden]
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.