On Fri, May 30, 2014 at 9:52 AM, Andrey Semashev wrote:
Is there a reason for it?
Andrey, John: My motivation was that it fits in the category of compiler/standard library feature detection useful for Boost library authors who only want that particular feature of Boost.Integer and prefer not to pull in boost::<integer types> just for that detection.
I have no problem if cstdint.hpp is moved as a whole, including its docs and tests. It seems, it only depends on Boost.Config (except for Boost.Detail in tests). What I wouldn't like is to split it into different headers across different libraries. As I mentioned, cstdint.hpp is supposed to reflect cstdint, so it should provide all the typedefs.
Hmm, I guess the question is where will users expect to find the docs/tests for that file? My guess is that it's probably not in config, but I may be wrong.... John.