I this post I give an introduction to the rules for generic programming in C++. Generic programming is from my point of view the outstanding feature and the future of C++. Hence it follows, that this and the upcoming posts are about the future of C++.

Making objects or methods const has two benefits. First, the compiler will complain when you break the contract. Second, you tell the user of the interface that the function will not modify the arguments.

If you can't throw an exception and can't use final_action (finally) from the guideline support library, you have a problem. Exceptional states require exceptional actions: goto. Really?

I have prepared the pdf bundle. To get it is quite simple.

To make my point clear, this post is about the exceptional case that you can not throw an exception. If your program runs in a restricted embedded environment or you have to fulfil a hard-real-time requirement, this situation may be not so exceptional to you.

Bartłomiej Filipek, author of the well-known C++-blog: Bartek's coding blog gave me four vouchers for his book C++ in Detail.

Based on my book "Concurrency with Modern C++" educative.io created an interactive course. You can have it now at a discount of 38 %.

"Modern C++ Concurrency" is a interactive journey through current and upcoming concurrency in C++.

• C++11 and C++14 have the basic building blocks for creating concurrent or parallel programs.
• With C++17 we got the parallel algorithms of the Standard Template Library (STL). That means, most of the algorithms of the STL can be executed sequential, parallel, or vectorized.
• The concurrency story in C++ goes on. With C++20 we can hope for extended futures, coroutines, transactions, and more.

Today's post is about the right way to throw and catch exceptions. This means in particular when you should throw and how you should catch an exception.

If you skim through the remaining rules to error handling, you often read the word noexcept. Before I write about the rules to error handling, I write first about the noexcept specifier and the noexcept operator in this post. 

My original plan was it to write in this post about the next rules to error handling. But I changed my plan to write about the future: contracts in C++20.