[boost] [config] What to call macros to indicate deprecated/removed components

Subject: [boost] [config] What to call macros to indicate deprecated/removed components
From: John Maddock (jz.maddock_at_[hidden])
Date: 2017-04-16 10:57:01

We now have several former C++ features which are removed in C++17:

auto_ptr

random_shuffle

binders

unary/binary_function

And we're getting requests for configuration macros for these, the 
question is what to call them?

We could stick with the (easy to implement) existing naming and just use:

BOOST_NO_<FEATURE>

or we could use:

BOOST_<STD>_REMOVED_<FEATURE>

which is a bit more work as all the scripts that rely on the 
BOOST_NO/BOOST_HAS convention need updating.

Any other suggestions/preferences?

Thanks, John.

---
This email has been checked for viruses by AVG.
http://www.avg.com