Subject: Re: [boost] Libraries and C++ compliance
From: Paul Fultz II (pfultz2_at_[hidden])
Date: 2017-04-10 14:35:13
> On Apr 10, 2017, at 9:05 AM, Edward Diener via Boost <boost_at_[hidden]> 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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk