C++ Core Gudelines: goto considered Evil
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?
This author has not written his bio yet.
But we are proud to say that Rainer Grimm contributed 691 entries already.
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.
If you skim the remaining rules to error handling, you often read the word noexcept. Before I write about the rules for error handling, I will write 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.
Error handling is an essential part of writing good software; therefore, the C++ core guidelines have about 20 rules for error handling.
Now, it’s time to choose the next pdf bundle? You will get all posts, all source files, and a cmake file to the chosen topic.
Today, I will finish my story on concurrency and lock-free programming. There are four rules to lock-free programming in the C++ core guidelines left.