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 provide a lot of checks which can be performed at compile time. With these posts, I will prove my statement.
static_assert is the tool in modern C++ to make your code safe.
The initialization of variables was unified 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 of 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 was so much prejudice against the usage of C++ in embedded programming. Most are based on a wrong understanding of the programming language C++.
Bjarne Stroustrup’s FAQ makes it crystal clear. One of the design goals for C++11 was to make C++ even better for the embedded world.
The new time library is an important component of the threading interface. As well, as threads, locks, and condition variables understanding time. All four have in common that they can sleep, wait or block until a time point or for a 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.
Time duration is the difference between two time points. It will be measured in time ticks.