
14 Oct
2013
14 Oct
'13
10:26 a.m.
On 14 October 2013 02:52, Edward Diener
I would have used the BOOST_WORKAROUND macro but clang does not support a value which gives a single number for the compiler version so I felt that drumming up multiple BOOST_WORKAROUNDs using major/minor/patch version numbers was too much of a hack to bother about.
It's not recommended to use Clang version numbers at all: http://lists.boost.org/Archives/boost/2011/06/182574.php I suppose using them in combination with checking for _MSC_VER is safe at the moment, but might not always be.