Re: [boost] [config] Add BOOST_NO_RANGE_BASED_FOR macro?

Subject: Re: [boost] [config] Add BOOST_NO_RANGE_BASED_FOR macro?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2012-07-10 09:44:08

On Tue, Jul 10, 2012 at 4:03 AM, John Maddock <boost.regex_at_[hidden]> wrote:
>> (Putting his money where his mouth is)
>>
>> Here's a patch vs. the trunk which renames all the macros in the table
>> "Macros that describe C++11 features not supported" (with the notable
>> exception of >BOOST_NO_LONG_LONG) to have consistent names.
>> For example:
>> BOOST_NO_VARIADIC_MACROS --> BOOST_NO_CXX11_VARIADIC_MACROS
>>
>> All the old names are then #defined to be the same as the new names;
>> All the code and tests in config has been updated to use the new names.
>> All the old names have been put into the "Boost Deprecated Macros" table.
>>
>> The goal here is no changes to client code (including code in boost
>> outside of the config library).
>> This seems to work fine on my system (Mac with gcc and clang)
>>
>> Now Beman can define "BOOST_NO_CXX11_RANGE_BASED_FOR" and it will match
>> the style with other macros.
>>
>> Comments?
>
>
> Based on casting a mark 1 eyeball over the diffs, I'm happy with that going
> in.

OK, I'm on board.

I'll wait until Marshall applies his patch before adding the
range-based-for-statement macro.

I noticed that clang's feature macro shortened the name to
"range_for". Does anyone object to BOOST_NO_CXX11_RANGE_FOR as our
macro name?

--Beman