[Thread] Perennial rw_mutex question

What is the status of rw_mutex and its brethren? It's been languishing on the thread_dev branch for far too long, but lots of people (myself now included) need it. Are there design issues holding it up? Some coding that still needs finishing? Testing? Doug

I have a somewhat modified version that I've been using for quite some time (a couple of years). I was planning to 1) check the changes into the thread_dev branch for people to look at, 2) query this mailing list about the changes, then 3) move whatever was agreed upon on into the main branch. I was planning to do this after I finished a couple of other Boost.Thread tasks, but I can move up steps 1) and 2) if it's really in demand. Look for it later today or perhaps tomorrow. Mike "Douglas Paul Gregor" <gregod@cs.rpi.edu> wrote in message news:20040504145217.A29785@barbara.cs.rpi.edu...
What is the status of rw_mutex and its brethren? It's been languishing on the thread_dev branch for far too long, but lots of people (myself now included) need it. Are there design issues holding it up? Some coding that still needs finishing? Testing?
Doug _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On Tue, 4 May 2004, Michael Glassford wrote:
I was planning to do this after I finished a couple of other Boost.Thread tasks, but I can move up steps 1) and 2) if it's really in demand. Look for it later today or perhaps tomorrow.
I'm interested, but it's not time-critical. Thanks. Doug

"Douglas Paul Gregor" <gregod@cs.rpi.edu> wrote in message news:20040504154323.G29785@barbara.cs.rpi.edu...
On Tue, 4 May 2004, Michael Glassford wrote:
I was planning to do this after I finished a couple of other Boost.Thread tasks, but I can move up steps 1) and 2) if it's really in demand. Look for it later today or perhaps tomorrow.
I'm interested, but it's not time-critical. Thanks.
I've checked these changes into the thread_dev branch (rw_lock.hpp, rw_mutex.hpp, rw_mutex.cpp). Anyone who is interested please take a look and comment. Major changes (see change logs in the files themselves for additional details): * Add lock promotion and demotion. * Rename to improve consistency and eliminate abbreviations: Use "read" and "write" instead of "shared" and "exclusive". Change "rd" to "read", "wr" to "write", "rw" to "read_write". * Change try lock & timed lock constructor parameters for consistency. * Add many assertions to test validity of mutex state and operations. Things still to be done (any help with these tasks would be greatly appreciated): Update documentation Update tests Mike
participants (2)
-
Douglas Paul Gregor
-
Michael Glassford