Archive for category: C++ Core Guidelines

creation of man

C++ Core Guidelines: Declarations and Initialisations

January 12, 2018

/

Let's continue our tour through the rules for expressions and statements in the C++ core guidelines.…

naming standards clean code 24 728

C++ Core Guidelines: Rules for Expressions and Statements

December 29, 2017

/

There are many rules in the C++ Core Guidelines dealing with expressions and statements. To be precise,…

relay race

C++ Core Guidelines: Passing Smart Pointers

December 23, 2017

/

Passing smart pointers is a critical topic that is seldom addressed. This ends with the C++ core guidelines…

gold 513062 640

C++ Core Guidelines: Rules for Smart Pointers

December 15, 2017

/

There were a lot of C++ experts who said that smart pointers were the essential feature of C++11. Today,…

German Monopoly board in the middle of a game

C++ Core Guidelines: Rules for Allocating and Deallocating

December 8, 2017

/

The guidelines have six rules for explicit memory allocation and deallocation. Six! Maybe you are surprised…

photo montage 1548599 640

C++ Core Guidelines: Rules about Resource Management

December 1, 2017

/

This and the following posts will probably be about the most critical concern in programming: resource…

hand 162127 640

C++ Core Guidelines: Rules for Enumerations

November 24, 2017

/

The section to enumerations has eight rules. Since C++11, we have scoped enumerations which overcome…

Wolpertinger

C++ Core Guidelines: Rules for Unions

November 17, 2017

/

A union is a particular data type where all members start at the same address. A union can hold only…

genetic

C++ Core Guidelines: More Rules for Overloading

November 10, 2017

/

I started the last post on my journey through the rules for overloading functions and operators. Let…

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…

Latest news

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 […]
Deferred Reclamation in C++26: Read-Copy Update and Hazard PointersJanuary 27, 2025 - 12:23 pm
Before I dive into lock-free programming, there’s a little bit of theory necessary. A common problem in concurrency is the so-called ABA problem. That means you read a variable twice, which returns the same value each time, A. Therefore, you conclude that nothing changed in between. But you forgot the B. Let me first use […]