If you haven't lived in a cave for the last few months, you've probably noticed that Microsoft has recently updated it's C++ compiler with the release of Visual Studio .NET 2003 (don't you just love MS product naming). This was a major upgrade of the compiler and has dramatically improved standard compliance. Having several million lines of code to play with (of which few million are compiled on non-Windows platforms using gcc), and after 6+ months of usage (since first public beta) I can't say I am not satisfied with it, but there are still a lot of small quirks to resolve. This is natural because the span between last two versions has been too big - previous version was issued in 1998(!) with Visual Studio 6. That means that in the meantime there was no real massive code base to test compiler with, while all along gcc was slowly upgraded will zillions of people using (testing) it every day. Handling boost and loki is just not good enough measure - in our real-life usage scenario of both libraries and other code using them (not only libraries' regression tests) I've seen several instances where compiler got confused just by changing the order of included files (especially from boost). I've also found at least one easy to reproduce bug that produces ICE yet is very simple (far more complicated code compiles without a glitch). Good news is that all problems I've seen can be worked around in a relative simple way, so switch is a must for users of version 6 and .NET (a.k.a 2002). One more bizarre fact - by default, compiler does not impose strict standard conformance. If you however do turn it on fully (/Za), you'll get zillions of errors in MFC and other MS code!