Boost logo

Boost :

From: John Maddock (john_at_[hidden])
Date: 2005-09-09 06:44:14


> So, do we yank read_write_mutex from 1.33.1 and, err, start over?

Heaven only knows!

Well, I guess read_write_mutex isn't much use as it is: basically I think it
tries to be too clever for it's own good.

Ultimately, since there is a rewrite in progress, then yes I think a rewrite
based upon a proven design *and not deviating from or extending that design*
would be a good thing. It's probably the only way to get a provenly correct
implementation, that can be maintained if necessary by someone other than
it's original author if necessary.

The trouble is what do we do with 1.33.1? We could either revert to the
1.32 version (if that is actually reliable, the current regression tests
don't show up these problems so we don't really know), or we could yank it
out of Boost entirely. I'm leaning towards yanking it out at present, but
it's a drastic step, and this presupposes that the original authors of the
class can't temporarily fix things for 1.33.1 (they all look to have either
gone away or be too busy at present however).

What do other folks think?

John.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk