Modernes C++

This page is the starting point for my blog Modernes C++. A simple overview of my existing and upcoming posts.

Read more
Views: 103645

Asynchronous Callable Wrappers

std::packaged_task enables you to write a simple wrapper for a callable, which you can invoke later.

Read more
Tags: tasks
Views: 27555

Asynchronous Function Calls

std:.async feels like an asynchronous function call. Under the hood std::async is a task. One, which is extremely easy to use.

Read more
Tags: async, tasks
Views: 96516

Tasks

Tasks were one of the latest additions to the C++11 standard. They give you a better abstraction than threads. In the general case, they should be your first choice. 

Read more
Tags: tasks
Views: 29016

Condition Variables

Condition variables allow us to synchronize threads via notifications. So, you can implement workflows like sender/receiver or producer/consumer. In such a workflow, the receiver is waiting for the sender's notification. If the receiver gets the notification, it continues its work.

Read more
Views: 72285

Thread-Local Data

By using the keyword thread_local, you define the thread local data. Thread-local can easily be explained in a few words.

Read more
Views: 30052

Thread-Safe Initialization of Data

In case the data is not modified when shared between threads, the story is simple. The data has only to be initialized in the thread safe way. It is not necessary to use an expensive lock for each access.

Read more
Views: 68802

Reader-Writer Locks

With C++14 came reader-writer locks. The idea is straightforward and promising. Arbitrary reading threads can access the critical region at the same time, but only one thread is allowed to write.

Read more
Tags: lock
Views: 57073

Prefer Locks to Mutexes

If the previous post showed something, it's, that you should use mutexes with great care. That's why you should wrap them in a lock.

Read more
Tags: lock, mutex
Views: 116786

The Risks of Mutexes

Usage of mutexes seems extremely simple. There is a critical section in the code, which can only be accessed by a single thread at any point of time. It's ensured by a mutex m. The calls m.lock() and m.unlock() guarantee this exclusivity. But, the devil is in the details.

Read more
Tags: mutex
Views: 23857

My Newest E-Books

Course: Modern C++ Concurrency in Practice

Course: C++ Standard Library including C++14 & C++17

Course: Embedded Programming with Modern C++

Course: Generic Programming (Templates)

Course: C++ Fundamentals for Professionals

Subscribe to the newsletter (+ pdf bundle)

Blog archive

Source Code

Visitors

Today 4560

Yesterday 7135

Week 36309

Month 46856

All 6275328

Currently are 209 guests and no members online

Kubik-Rubik Joomla! Extensions

Latest comments