Andrew Stitcher wrote:
Doing some research on the c++ semantics of volatile recently I came
across this rather relevant article again.
I think that there are some important ideas in here that could help us
greatly reduce the chance of race conditions where we're using mutexes
to encapsulate critical sections.
http://www.ddj.com/cpp/184403766
Agreed, very good article. I've been marking "internal" functions that should
only be called with a lock already held by adding a dummy extra Locker&
parameter which is ugly and doesn't have as much expressive power.
Definitely something we should adopt post GA.
