7 Jun
2015
7 Jun
'15
10:25 a.m.
On 07.06.2015 11:39, Vicente J. Botet Escriba wrote:
Le 05/06/15 09:41, John Maddock a écrit :
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?
This PR makes Boost.Config depend on all the related Boost libraries creating a whole cycle and modularity will be broken.
These headers don't add a dependency since they don't include headers of the related libraries. They only define macros.