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.

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.

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

With the new C++11 Standard, C++ faces the first time the challenges of multicore architectures. The 2011 published standard defines how a C++ program has to behave in the presence of multiple threads. The C++11 multithreading capabilities are composed of two components. This is on the one hand, the defined memory model, which is on the other hand, the standardized threading interface.

Since half a year I have a blog about modern C++: Modernes C++. Although 80% of the readers are used to English, the blog is written in German. So I decided to translate the articles successively in English. Because my English is not as good as my German I asked a few people for help. They will proofread the syntax of my articles. Now I have a few volunteers and I'm ready to start. I will still write my articles in the first place in English, but my hope is, that the German and English articles are in lockstep in half a year.
Because the roots of my blogs are in German, I will continue to call him Modernes C++. That is not by mistake.