The Biggest Changes in C++11 (and Why You Should Care)
blog.smartbear.com
blog.smartbear.com
that's a bit of a strange statement, no? Since when is a GUI or even an XML API part of the core language features? And adding reflection would, erm, kinda mean that every compiler has to be rewritten almost from scratch.
Given that C++ libraries are getting so complex (now with move semantics!) there is no way a library user can understand why something does not work as expected. Especially when dealing with sophisticated libraries: Boost, Eigen, etc.
As far as I understood it, this was merely due to discussions what types of Concepts would be supported. There was one group of people that wanted very granular Concepts, and another group of people that wanted just very broadly defined Concepts. They never reached an agreement on this.
I already use it for some little new projects. I'm sure a lot of legacy stuff won't be able to move on to the new standard for a while because they need backwards compatibility with old compilers though.
I'm itching to start using this stuff in QuickBooks; I love smart pointers but hate auto_ptr and being able to safely use STL containers with smart pointers opens a new world of entity processing.
The apache table[+] has been updated as of this month, and MSVC (with a version given as "11.0 nov'12") now is looking rather better, but is still missing constexpr... :(
Still, it appears that there should be fairly good support in all major compilers within the next few years, at least if you can depend on your devs using relatively up-to-date compiler releases (not at all a given where I work!)... :]