
On 6/5/2015 6:15 AM, Sylvester-Bradley, Gareth wrote:
On 05 June 2015 10:30, Edward Diener wrote:
On 6/5/2015 3:41 AM, John Maddock wrote:
There is a pull-request for Config to provide support for switching between boost:: and std:: library equivalents: https://github.com/boostorg/config/pull/63
My questions are:
* Is this the right approach? And, * Is Boost.Config the right place for it?
Thanks for your comments, John.
That is my pull request so I will comment now that you have so graciously provided a forum for my idea.
I don't know what "the right approach" would be but this is one approach that does work easily, following the documentation I have written about it and added to the Boost.config documentation.
[snip good detection/reporting macros stuff]
3) In code for that library's functionality use the namespace macro provided for accessing the library's functionality:
BOOST_CPP_XXX_NS::some_functionality etc.
It would be useful to compare the BOOST_CPP_XXX_NS macro approach to providing a namespace with using declarations. I use 'bst'.
You could just as easily write: using namespace BOOST_CPP_XXX_NS;
One advantage is flexibility to adapt the mapping where necessary, e.g. while Boost placeholders were in boost, but std::placeholders.