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 important part of writing good software; therefore, the C++ core guidelines has about 20 rules for error handling.
Today, I will finish my story to concurrency and lock-free programming in particular. There are four rules to lock-free programming in the C++ core guidelines left.
Today, I solve the riddle from my last post. Thanks to my readers, the analysis of the ABA problem is quite accurate.
Today, I finish the rules to concurrency and continue directly with lock-free programming. Yes, you have read it correctly: lock-free programming.
Today, I write a scary post about condition variables. You should be aware of this issues of condition variables. The C++ core guideline CP 42 just states: "Don't wait without a condition".
Concurrency provides many ways to shoot yourself in the foot. The rules for today help you to know these dangers and to overcome them.
When you create a new child thread, you have to answer an important question: should you wait for the child or detach yourself from it? If you detach yourself from the newly created child, and your child uses variables which are bound to your lifetime as creator a new question arises: Will the variables stay valid during the lifetime of the child thread?
If you want to have fun with threads, you should share mutable data between them. In order to get no data race and, therefore, undefined behaviour, you have to think about the synchronisation of your threads.
Today, I'm happy to write about the probably most important rule of the C++ Core Guidelines for concurrency: Whenever feasible use tools to validate your concurrent code. Not all, but a lot of bugs can be detected with tools and each fixed bug is a good bug. Here are two tools which provided me precious help in the last years: ThreadSanitizer and CppMem.
Currently are 226 guests and no members online
Kubik-Rubik Joomla! Extensions