Re: [boost] [RFC][threads] Header/namespace policy draft

From: John Maddock (john_at_[hidden])
Date: 2007-12-01 05:32:00

Joel de Guzman wrote:
> If the thread library's move function is undocumented, then it has
> no business being in the root boost namespace but in boost::detail.
> If indeed that is the case, I consider it a bug that should be fixed.
> We should be more vigilant in the review period on such violations.
> More stringent requirements should be put in place for core libraries.
> We should try to restrict as much as possible what goes into the
> boost root namespace and directory. I think it's best to add:
>
>     Only reviewed and documented components of a core library may be
>     placed in the root boost namespace. Violations are considered bugs
>     that must be fixed.
>
> in our core libraries policies.
>
> ((I did a quick search in boost thread's docs and indeed move is not
> documented.))

100% agreement from me: "move" is such a common name that we can't afford to 
pollute namespace boost with it: unless we really mean to of course :-)

Unfortunately the Boost.Thread docs aren't up to date, so I'm not sure what 
Anthony intended here: Anthony?

Regards John.