----- Original Message -----
From: "Edward Diener"
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.
I submitted pull requests, directly on 'master', for chrono, regex, threads, and test to fix the warnings problem. But it appears to be too late for 1.56.
I understand your being upset by all the warnings, and perhaps users will not like them when they build Boost 1.56 with clang, but there are worse things that can happen in a new release.
Are these just warnings, but the results are still correct? Either way, this is a clang issue. They intentionally chose to *not* implement the standard instead deferring to the garbage MSVC status quo. Given that and their attitude of "more" being put above "better", a sea of warnings is a good thing. Regards, Paul Mensonides