You can subscribe to our newsletter too!
Meeting C++ Newsletter - April 2013
this is Meeting C++ April newsletter. This time the focus is on C++14, which has now taken shape at the C++ Committee Meeting in Bristol. While I wrote a series about the Papers for Bristol, I did not attend the Meeting it self, so that I cannot report my personal view on the results and the Meeting yet. But, I think its very good, that the tracks for C++14 are now laid, and its more clear now, in which direction C++ goes after C++11. There are two very good trip reports, one from Herb Sutter and one from Michael Wong.
So, what will be the key features of C++14?
replacing new and delete with Smartpointer is now a lot easier in C++14, with make_shared/make_unique you can make all of the needed smartpointer types. No need to use new or delete.
C++14 will offer binary literals, with the same syntax as in Java7, Python and D: 0b01101111
Return type deduction for normal functions
What you already could do with lambdas in C++11, let the return type be deduced by the compiler and use auto as the return type for any function. This is part of the goal to make lambdas, functions and function objects more unified in their features.
Runtime sized arrays
C++14 will offer runtime sized arrays, making it possible to allocate arrays at run time on the stack. This can be very practical, still std::vector or the new dynarray might be a better approach. Also the run time sized arrays are very restricted in their type interface. This proposal still leads to very controversial discussions.
Also C++14 will offer a new STL type called std::dynarray, which will offer a fixed array allocated at compile/run time. DynArray is similar to the run time sized arrays, but offers a more stl like interface, and is library only, not changing the language.
C++14 will offer its own optional type, which is very similar to boost::optional.
C++14 will offer a std::shared_mutex, allowing a better locking in its threading implementation. This is a completion of the locking feature for C++11.
relaxation of constexpr
There is a number of new features for constexpr allowing to do much more with constexpr in C++14 then in C++11. For example there is now constexpr variables, which can be calculated at compile time, which allows to replace static variables in templates calculated at compile time, for example std::numeric_limits
There is a number of other new features and changes to C++14, and some minor additions might still come with the fall meeting in Chicago on board, but the C++14 Standardisation is now on its way, and it is very clear: There will be a new C++ Standard by next year!
Meeting C++ 2013 Conference
As usual, a list of good C++ Links from April...
Status of the C++11 Migrator Project at Clang
An interview about OpenMP with Michael Wong.
Connecting to multiple Redis Servers with C++
Ten C++11 features every C++ Developer should know
Tracey - a lightweight C++11 memory leak finder
clReflect - natural C++ Reflection with clang
Releasing Wt 3.3.0