13 Jun
2015
13 Jun
'15
5:02 p.m.
Yes, that would be the objection from my side, at least. I don't want to include a whole std header to check for a single feature that may be implemented in it. And I want Boost.Config to include most of STL even less.
And the rationale for this is what ? Compile-time computer cycles ?
The effect is measurable, at least on cygwin GCC-4.9.2, I see: Current Config Size: 21K, times: real 0m0.279s user 0m0.030s sys 0m0.233s Config plus headers required for current SD6: Size 2Mb, times: real 0m1.092s user 0m0.593s sys 0m0.467s I would expect the effect to get worse as more SD6 macros are added to other headers. John.