13 Jul
2012
13 Jul
'12
8:23 a.m.
is there a way to don't include all the deprecated macros? Whoa - interesting question. I don't know of one.
However, all the deprecated macros are defined (I _believe_) in one place, in boost/config/suffix.hpp Making it so none of them are defined _should_ be straightforward.
Could I suggest to define all of them in a specific boost/config/deprecated.hpp file, so that we can add a deprecated warning when the file is included.
I think it's too soon for that - as things stand you would basically be injecting that warning into every Boost header that includes boost/config.hpp. Besides I don't see what harm defining the old names does? John.