In this post, I continue my journey through the rules to performance in the C++ Core Guidelines. I will mainly write about design for optimisation.
Five bloggers have teamed up around the world to deliver an April Fool's joke to readers about eliminating pointers. The response to the five articles was huge and ranged from "it took so long" to "that can not be true". Here again the truths, half-truths and untruths: No New New: Raw Pointers Removed from C++. You can even read this post in German or in Russian.
Two weeks ago, the ISO C++ standard meeting took place in Jacksonville. Today I want to make a short detour and write about the revolutionary decision that was made in the Jacksonville meeting. Additionally, I refer to the post C++ Will no Longer Have Pointers by Fluent C++. The standard committee decided that pointers will be deprecated in C++20 and will with very high probability be removed in C++23.
Before I write about the rules of performance I will do a very simple job. Accessing the elements of a container one by one.
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 write about the remaining rules to statements and the arithmetic rules. If you don't follow the arithmetic rules, undefined behaviour may kick in.
My last German post C++ Core Guidelines: To Switch or not to Switch, that is the Question got a lot of attention. To use a hash table instead of a switch statement seems to be a highly emotional topic. So I change my original plan. Today, I will present different kinds of control structures. I will start with the if and switch statements, continue with the hash table, and end with dynamic and static polymorphism. Additionally, I will mark a few remarks about performance and maintainability.
Currently are 213 guests and no members online
Kubik-Rubik Joomla! Extensions