10 Apr
2017
10 Apr
'17
3:27 p.m.
AMDG On 04/10/2017 08:35 AM, Paul Fultz II via Boost wrote:
On Apr 10, 2017, at 9:05 AM, Edward Diener via Boost
wrote: As a side note I would really like to see libraries, which are tailored for Boost, use the Boost Config C++ feature testing macros to put out preprocessor #error messages when a feature that it needs is not supported during compilation, rather than letting the compiler simply fail because the construct in code cannot be parsed at the C++ conformance level the code expects.
This should happen during configure step, so that the user gets an error before even building the library.
That works for libraries that have a configure step, which is not most Boost libraries. In Christ, Steven Watanabe