On Tue, Apr 5, 2016 at 2:02 PM, degski
All this talk of yours about how conformant to the C++ standard Microsoft is becoming means nothing unless they can fix the preprocessor. The rest of your touting of how serious Microsoft is in conforming to the C++ standard is just "show business" to me. Whatever Microsoft ships as their backend compiler, whatever noises they make about being serious about conforming as closely as possible to the C++11 or C++14 or C++17 standards, if they can't ship a C++ standards preprocessor they will never be conformant to the C++ standard.
It seems google is happy https://randomascii.wordpress.com/2016/03/24/compiler-bugs-found-when-portin..., maybe boost should tell them that you're unhappy with the preprocessor and where it's buggy?
I don't think Google is an adequate example. From what I've seen, their coding policy is rather primitive and until recent attempts to cautiously use select C++11 features it was mostly C with classes. Boost, on the other hand, has always used C++ to its full power. No wonder that many weaker compilers choke at Boost.