AMDG Jérémy Coulon wrote:

According to the documentation of Boost 1.34 (before the major rewrite of boost::thread), the read/write lock was offering different scheduling policies. Some of those policies were providing a solution to the starvation problem that usually occurs with this kind of lock.

http://www.boost.org/doc/libs/1_34_1/doc/html/thread/concepts.html#thread.co...

http://www.boost.org/doc/libs/1_34_1/doc/html/thread/concepts.html#thread.co...

But I don't find any reference to starvation and scheduling policies in the current Boost documentation (1.37).

So, I am wondering if this starvation problem is solved in the current boost::thread implementation ? What scheduling policy is actually the default one ? Can the documentation be improved ?

I believe that the current implementation should not starve readers or writers. In Christ, Steven Watanabe