Blog

Chrono: Input

June 24, 2024

You can also apply the format specifier for formatted input. This post is the eleventh in my…

Chrono I/O: Unformatted and Formatted

June 17, 2024

Chrono I/O consists of reading and writing chrono types. The various chrono types support unformatted…

My ALS Journey: 10/n

June 10, 2024

Wow! This is already my 10 status report. >> My ALS Journey so far << How I write…

Chrono I/O

May 20, 2024

Chrono I/O consists of reading and writing chrono types. The various chrono types support unformatted…

Time Zones: Online Classes

May 13, 2024

Today, I will continue to present the functionality of the time zones of the C++20 chrono extension. This…

TimelineCpp20CoreLanguage

Time Zones: Details

May 6, 2024

/

Today, I present the time-zones functionality of the C++20 extension. This post is the seventh…

My ALS Journey: 9/n with Hector

April 29, 2024

I initially thought that this status report was not particularly exciting. I was very wrong, but read…

C++20: Query Calendar Dates and Ordinal Dates

April 22, 2024

The extended chrono library makes it relatively easy to ask for the time duration between calendar dates. This…

C++20: Displaying and Checking Calendar Dates

April 15, 2024

I created calendar dates in my last post, "C++20: Creating Calendar Dates," and I will display and check…

C++20: Creating Calendar Dates

April 8, 2024

In this post, I will dive deeper into calendar dates and create them. If this post is too overwhelming…

My ALS Journey: 8/n with Easter Present

March 30, 2024

I'm happy to announce the second money-raising campaign for ALS research. This time, I'm proud to say…

C++20: Time of Day

March 25, 2024

This new data type std::chrono::hh_mm_ss in C++20 stands for the time of day. Time of Day std::chrono::hh_mm_ss…

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