Howard Hinnant wrote:
Here is a link to a reference implementation and a FAQ for mutexes, locks and condition variables I am currently anticipating proposing for C++ standardization (or subsequent TR).
http://home.twcny.rr.com/hinnant/cpp_extensions/concurrency_rationale.html
I may have overlooked it ( in which case I would be glad to be told ) but I am wondering why the following feature isn't considered: If a thread somewhere is blocked in a wait for a condition, sometimes I find myself in a need to wake it up unconditionally. E.g. I want to signal it should stop whatever it is currently doing and at next possible chance e.g. restart. Or abort an pending IO operation and try with another IO option. This is an easy objective if I know on which condition the thread is blocked, but close to impossible if I do not know. Yes cancellation fits part of this bill, but then the thread is gone, which is not what I need. Roland aka speedsnail