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

On 16 April 2017 at 11:57, John Maddock via Boost wrote:

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.

No strong opinion, but do we want the default to be that they're available?