Subj : Re: C++ and lock-free To : comp.programming.threads From : Joe Seigh Date : Mon Sep 19 2005 10:55 am Chris Thomasson wrote: > "Joe Seigh" wrote in message > news:GfOdnXs-7-OFE7feRVn-uQ@comcast.com... > >>If C++0x ever gets out of being stuck in an infinite loop on >>the memory model, where does anyone think C++ is going on lock-free > > > Wouldn't it be a bit complicated to create a truly lock-free version of the > STL? I believe that a lock-free read version of the STL would be doable. > But, even then... They could run into some problems with iterating threads > observing that an object is in a STL collection "after" it has been removed > by another thread. However, we all know that this is completely normal > behavior wrt algorithms like VZOOM, RCU, SMR, ect... > > ;) > > > I believe these subtitle differences could be in conflict with some existing > designs; C++ might have some big problems here? > The semantics are different. So there would be a learning curve on implementing it and using it. But they aren't even anywhere near to beginning that. They're bogged down in preliminaries. So the curve isn't a curve, it's a flatline. > >>the stuff Herb Sutter keeps mentioning but I've > > > What kind of stuff is that? > I don't know. He hasn't said what it is or at least given any non-trivial examples. -- Joe Seigh When you get lemons, you make lemonade. When you get hardware, you make software. .