On 3 Aug 2014 at 18:53, Edward Diener wrote:
I do not feel empowered to make this call myself, since a change to the guts of Boost PP config.h affects every library using Boost PP. But I am confident it should work in theory. But if some library is using Boost PP variadic macros and doesn't have the clang equivalent option set that turns on C++0x or better support then that library will fail.
I think turning off variadic macros for clang would be a retrograde step considering the much superior alternatives.
OTOH we could look for the libraries that have '<warnings>all' in their jam files and create pull requests so that it gets changed to <warning>on whenever clang is the compiler. Something like:
'<toolset>clang:<warnings>on' as a project requirement I suppose.
As far as end-user using Boost libraries, other than building them, with clang they would only see the clang warnings if they specify '-pedantic' and the library used variadic macros.
For a 1.56 release, this seems like a very sensible least cost solution. It breaks nothing, is easy to do, and can be done immediately. Later on individual libraries can restore pedantic warnings for clang if they do whatever #pragma warning fixes necessary. Up to their maintainers. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/