Template Metaprogramming is programming at compile time. But what has template metaprogramming in common with the type-traits library? A lot! The type-traits library is pure template metaprogramming, tamed in a library. With this post my presentation of the type-traits library becomes more structured.

In the post Statically checked I wrote that the functions of the type-traits library are an ideal fit for static_assert. The reason is that static_assert requires a constant expression. The functions of the type-traits library provides a lot of checks which can be performed at compile time. With this posts I will prove my statement.

static_assert is the tool in modern C++ to make you code safe.

The initialization of variables was uniformed in C++11. The rule is quite simple. {}-Initialization is always applicable. 

Probably the most frequently used feature of C++11 is auto. Thanks to auto the compiler determines the type of a variable from its initializer. But what is the point with safety critical software? 

After the myths the facts will follow. Therefore, we leave the area of half truth and untruth statements about C++.

As I started working in the embedded environment I was astonished that there were so much prejudice against the usage of C++ in the embedded programming. The most are based on a wrong understanding of the programming language C++.

Bjarne Stroustrups FAQ makes it crystal clear. One of the design goals for C++11 was it to make C++ even better for the embedded world.

The new time library is an important component of the threading interface. As well threads, locks, condition variables as future have an understanding of time. All four have in common that they can sleep, wait or block until a time point or for a time duration.

A clock consists of a starting point and a time tick. C++ offers with std::chrono::system_clock, std::chrono::steady_clock, and std::chrono::high_resolution_clock three clocks.