Linked by Thom Holwerda on Sun 9th Sep 2007 18:08 UTC, submitted by koki
BeOS & Derivatives "The primary intention of my previous article was to make it very clear why and when locking is needed in multithreaded applications. In this article, I want to present my experiences in writing a new prototype for a replacement of the document model in WonderBrush and how it is manipulated and rendered asynchronously."
Permalink for comment 269946
To read all comments associated with this story, please click here.
Member since:

Writing multithreaded applications in C++ is like pulling teeth.

I don't agree. The problem is that a lot of developers just won't or will not understand multi-threading. Using a language that "hides" the locking & message passing details may help mitigate that problem somewhat, but they'll still have very little idea of how it works.

Writing multi-threaded C++ is easy. There are three or four rules to remember and that's about it. Any developer should be capable of it.

Reply Parent Score: 7