There is a config pull request outstanding that includes .
If it was almost any library other than config, I'd apply this without a
second thought. But Boost config is special in that if it breaks, virtually
the whole of boost breaks. So it makes sense to be cautious about
dependencies. Has there been any discussion about the relationship between
Boost.config and Boost.predef?
Even if we accept the patch, is the right header? It just
forwards:
#include
#include
#include
#include
#include
#include
#include
The rationale for the pull request is a need in other Boost libraries to
detect Windows platform variants like BOOST_PLAT_WINDOWS_DESKTOP
andBOOST_PLAT_WINDOWS_RUNTIME. Boost.Predef does a nice job of that.
But the
only header strictly needed is .
So the desired effect can be achieved several ways:
1) #include in the include/boost/config/platform/ headers.
2) #include in the include/boost/config/platform/
headers.
3) #include in the files that actually use the desired
macros.
4) #include in the files that actually use the
desired macros.
If I had been writing the code myself, I probably would have selected
option (4). What do others think?
--Beman
