[Boost-users] Re: boost::read_write_mutex simple usage question.

Michael Glassford wrote:

Gordon Smith wrote:

...

The following code seems to deadlock on the second (read) scoped lock (not what I would expect):

[snip]

There are some definite problems with read_write_mutex in the 1.31 release and this is one of them. Unfortunately the unit tests were quite lacking and didn't catch a bug as simple as this.

This fix is now checked in, as well as expanded unit tests. As I indicated before, I'm not very happy with the read/write mutex (it's too too complex--and therefore error-prone--and takes up more memory than I would like). The design should be redone when the new interface is implemented. Mike