In the last post C++ Core Guidelines: Type Erasure, I presented two ways to implement type erasure: void pointers and object orientation. In this post, I bridge dynamic polymorphism (object orientation) with static polymorphism (templates) to get type erasure with templates.
The rule “T.5: Combine generic and OO techniques to amplify their strengths, not their costs” of the core guidelines to generic programming uses type erasure as an example. Type erasure? Really! Of course, it takes me two posts to explain this advanced template technique.
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.
I have prepared the pdf bundle. To get it is quite simple.
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?
Bartłomiej Filipek, author of the well-known C++-blog: Bartek’s coding blog gave me four vouchers for his book C++ in Detail.
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.
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 an 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 […]
Today’s post is about the right way to throw and catch exceptions. This means when you should throw and how you should catch an exception.