Re: [boost] [config] C++0x macros

From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-05-27 11:23:29

John Maddock wrote:
> Beman Dawes wrote:
>> There is a practical limit on the length of names because the config
>> mechanism uses them for file names. But perhaps we can make them less
>> cryptic, and still hold them to a reasonable length, say 32
>> characters.
> 
> It's not absolutely essential for the test filenames to have the same name 
> as the macro - as long as you can find one from the other :-)
> 
> Personally I'd go for more descriptive names as well,

That's my preference too, so since we aren't limited by filenames, here 
is a more explicit set (taking into consideration comments from Doug and 
others):

BOOST_NO_DECLTYPE                       // no decltype
BOOST_NO_LONG_LONG                      // no [unsigned] long long type
BOOST_NO_RVALUE_REFERENCES              // no r-value references
BOOST_NO_STATIC_ASSERT                  // no static_assert
BOOST_NO_VARIADIC_TEMPLATES             // no variadic templates
BOOST_NO_SCOPED_ENUMS                   // no enum class
BOOST_NO_RAW_LITERALS                   // no raw character or string
                                         //  literals
BOOST_NO_UNICODE_LITERALS               // no Unicode literals
BOOST_NO_UNICODE_CHAR_TYPES             // no char16_t or char32_t
BOOST_NO_EXPLICIT_CONVERSION_OPERATIONS // no explicit operator T()
BOOST_NO_DEFAULT_FUNCTIONS              // no = default functions
BOOST_NO_DELETED_FUNCTIONS              // no = delete functions
BOOST_NO_CONSTEXPR                      // no constexpr

Iff voted into the WP:
BOOST_NO_CONCEPTS                       // no concepts

I'll do BOOST_NO_SCOPED_ENUMS, to make sure I've got the config process 
right, and then work on the others as time permits.

--Beman