Archive for year: 2017

stork 1324371 1280

C++ Core Guidelines: Rules for Copy and Move

September 15, 2017

/

The rules for copy and move are pretty obvious. But before I describe them I have to write about the…

RainerGrimmSmall

My open C++ Seminars in the First Half of 2018

September 13, 2017

/

Do you want to reach the next C++ level? Here are my open C++ seminars in the first half of 2018. Embedded…

stork 1324371 1280

C++ Core Guidelines: Constructors

September 8, 2017

/

The lifecycle of each object starts with its creation; therefore, this post will be about the thirteen…

RainerGrimmSmall

The new pdf bundle is ready: C++17

September 6, 2017

/

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

1024px Max und Moritz Busch 011

C++ Core Guidelines: Destructor Rules

September 1, 2017

/

Does my class need a destructor? I often heard this question. Most of the time the answer is no and you…

ConcurrencyCoverFrame

I Proudly present my Book is Ready “Concurrency with Modern C++”

August 31, 2017

/

Concurrency with Modern C++ is a journey through current and upcoming concurrency in C++. C++11…

RuleOfZeroFiveSix

C++ Core Guidelines: The Rule of Zero, Five, or Six

August 25, 2017

/

This post is about the rule of zero, five, or maybe six. I will also show the difference between copy…

Observer

C++ Core Guidelines: Class Rules

August 18, 2017

/

A class is a user-defined type where the programmer can specify the representation, the operations, and…

RainerGrimmSmall

Which pdf bundle should I provide?

August 15, 2017

/

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

cogs

C++ Core Guidelines: Semantic of Function Parameters and Return Values

August 11, 2017

/

Today, I conclude my treatise about the rules for functions in the C++ core guidelines. The last…

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 […]