Re: feature for C++ standards compliance

From: Edward Diener (eldiener_at_[hidden])
Date: 2021-02-25 21:13:54

On 2/25/2021 3:48 PM, Gavin Lambert via Boost wrote:
> On 26/02/2021 8:58 am, Robert Ramey wrote:
>> Right.  Still it's only 5 tests.  After tracking this down - which 
>> took a surprising amount of time given branches, etc - I considered my 
>> options and the easiest and most future looking was to just suppress 
>> these tests for compilations with C++ version <C++11.  It's a good 
>> simple, expedient solution.  I just needed an attribute to condition 
>> on.   As chris pointed out I can condition one boost version.  This is 
>> a practical and simple idea and I'll use it if nothing better comes up.
> 
> Conditioning a boost test on boost version < N is equivalent to just 
> unconditionally suppressing it, no?
> 
> Isn't the goal to only suppress it when not compiling >= C++11? 
> Shouldn't you just check __cplusplus >= 201103 for that?

Unfortunately __cplusplus is not totally reliable in a number of 
compiler implementations.