Subject: Re: [boost] Are some of the trunk regression tests running in C++0x mode when they shouldn't be?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-11-10 19:14:07
On 11/10/2011 03:30 PM, Gennadiy Rozental wrote:
> Vicente J. Botet Escriba <vicente.botet <at> wanadoo.fr> writes:
>> Le 10/11/11 21:13, Gennadiy Rozental a Ã©crit :
>>> Steven Watanabe<watanabesj<at> gmail.com> writes:
>>>>> Looks like -std=c++0x is being specified when it shouldn't for some reason?
>>>>> Is something broken, or am i imagining it?
>>>> This is a problem in Boost.Test as of r75372.
>>> How should I specify in Jamfile that I want to require c++11 support from gcc
>>> starting with version a.b.c?
>> You should not require this. Even if using a given version of gcc, users
>> could been to preserve a C++03 behavior.
> What is the problem with enabling C++11 features if possible? We do not expect
> backward compatibility issues, don't we?
The problem is that as a library developer,
it isn't your decision whether to enable it or not.
> What about MSVC? It has C++11 enabled by default.
> Some of the new features of Boost.Test require c++11 support. I want to be able
> to test it and I want users to be able to use it.
It's better to let users decide whether they
want C++11 support. For testing, just look
at the testers that have C++11 enabled. Most
of them have _0x in the name. For your own
testing you can pass cxxflags=-std=c++0x
on the command line.