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
Comments 1Views: 1566

Source Code Repository

I created a repository for the source code. It's on GitHub and has the name ModernesCppSource:
https://github.com/RainerGrimm/ModernesCppSource.git

Read more
Comments 1Views: 3830

Thread Creation

Thread creation is easy. Call  std::thread, and a new thread will be created. The thread gets a work package and starts it immediately. The creator of the thread (the Parent) has to take care of the created thread (the child). The Parent should wait until its child is done with its task or has to detach itself from its child. The child thread can get its payload task arguments by copy or by reference.

Read more
Comments 9Views: 5439

Threads Sharing Data

One of the biggest challenges of thread-management begins when the threads share non-const data

Read more
Comments 3Views: 2987

Thread Arguments

A thread gets its data by copy or by reference. Per default, you should use by copy. Why? In case your thread gets its data by reference, you have to be extremely careful about the lifetime of the arguments.

Read more
Comments 1Views: 2604

Threads Lifetime

The parent has to take care of its child. This simple idea has big consequences for a thread lifetime. The following program starts a thread, that displays its ID.

Read more
Comments 23Views: 4935

For the Proofreaders and the Curious People

After a lot of discussion with my proofreaders, we finally have a process to publish the articles.

Read more
Comments 11Views: 2253

My Newest E-Book

Latest comments

Subscribe to the newsletter (+ pdf bundle)

Blog archive

Source Code

Visitors

Today 138

All 279146

Currently are 193 guests and no members online