Archive for year: 2017

mistake

C++ Core Guidelines: Rules for Overloading and Overload Operators

November 4, 2017

/

There are ten rules for overloading and overload operators in the C++ core guidelines. Many of them are…

cover

The C++ Standard Library: The Second Edition includes C++17

November 3, 2017

/

Just updated: The C++ Standard Library: What every professional C++ programmer should know about the…

doorSmall

C++ Core Guidelines: Accessing Objects in a Hierarchy

October 27, 2017

/

There are nine rules to access objects in class hierarchies. Let's have a closer look. Here…

C++ Core Guidelines: The Remaining Rules about Class Hierarchies

October 20, 2017

/

I needed three posts to present the 20 rules for class hierarchies in the C++ core guidelines. Here are…

RainerGrimmSmall

The new pdf bundle is available: Functional Programming with C++17 and C++20

October 18, 2017

/

I have prepared the pdf bundle. To get it is quite simple. If you subscribe to the newsletter, you…

C++ Core Guidelines: More Rules about Class Hierarchies

October 13, 2017

/

In the last post, I started our journey with the rules of class hierarchies in modern C++. The first…

hierarchy 73335 640

C++ Core Guidelines: Class Hierarchies

October 5, 2017

/

Let's talk in this post about rules for class hierarchies in general and in particular. The C++ core…

Lambda

C++ Core Guidelines: Function Objects and Lambdas

September 29, 2017

/

I can not think about modern C++ without lambda expressions. So my wrong assumption was that there are…

RainerGrimmSmall

Which pdf bundle should I provide? Make your choice!

September 28, 2017

/

Now, it's time to choose the next pdf bundle? You will get all posts, all source files, and a cmake file…

scales 310962 640

C++ Core Guidelines: Comparison, Swap, and Hash

September 22, 2017

/

This post will be about comparisons, swap, and hash. That means I conclude with his post my treatise…

Latest news

A Lock-Free Stack: A Hazard Pointer ImplementationMarch 10, 2025 - 11:42 am
Hazard Pointers solve all issues of the previous implementation: A Lock-Free Stack: A Simple Garbage Collector. From one Week to two Weeks You may have already noticed. I will change my blog publishing frequency from one to two weeks in the future. Writing a post using your voice is exceptionally exhausting and time-consuming. Hazard Pointers […]
A Lock-Free Stack: A Simple Garbage CollectorFebruary 24, 2025 - 11:58 am
My next lock-free stack includes a simple garbage collector. I discussed the concurrent execution of more than one topAndPush call is a Race Condition. I can safely delete a node if not more than one topAndPush call is executing concurrently. This observation is crucial for solving this memory leak issue: I store removed nodes on […]
A Lock-Free Stack: Atomic Smart PointerFebruary 17, 2025 - 11:47 am
The easiest way to solve this memory leak issue from the last post is to use a std::shared_ptr. Atomic Smart Pointer There are two ways to apply atomic operations on a std::shared_ptr: In C++11, you can use the free atomic functions on std::shared_ptr. With C++20, you can use atomic smart pointers. C++11 Using atomic operations […]
A Lock-Free Stack: A Complete ImplementationFebruary 10, 2025 - 3:01 pm
My last lock-free stack implementation was incomplete. It only supported push operations. Let’s change this. The following paragraph about sequential consistency is optional. You can easily ignore it. Sequential Consistency In my examples, I use the default memory ordering: sequential consistency. The reason is simple. Sequential consistency provides the strongest guarantees of all memory ordering […]
My Next Mentoring Program: “Generic Programming (Templates) with C++” startsFebruary 4, 2025 - 4:51 pm
My next mentoring program, “Embedded Programming with Modern C++,” starts on January 31st. Registration is open. Here are more details. Embedded Programming with Modern C++ The mentoring program consists of 16 stations. You have to invest at least 3 hours per week for each one. This means the program takes four months, and you can […]
A Lock-Free Stack: A Simplified ImplementationFebruary 3, 2025 - 10:37 am
Today, I continue my mini story about lock-free data structures. General Considerations From the outside, the caller’s responsibility (application) is to protect the data. From inside, the data structure is responsible for protecting itself. A data structure that protects itself so a data race cannot appear is called thread-safe. First, what general considerations must you […]