|
Boost : |
From: Howard Hinnant (hinnant_at_[hidden])
Date: 2006-02-19 17:57:46
On Feb 19, 2006, at 1:40 PM, Ion Gaztañaga wrote:
> Currently, following Boost.Thread interface, mutex lock and unlock
> functions are private, but I would prefer making them public, and
> implement a unique scoped lock class that can lock any "lockable"
> object
> (shared_mutex, shared_recursive_mutex, named_mutex). This general
> locker
> could be moved to boost utilities or be just for this library. Or
> do you
> consider "too dangerous" to have lock functions public?. This is a
> proposal based on Howard Hinnant's much more complete scoped_lock
> proposal
> (http://home.twcny.rr.com/hinnant/cpp_extensions/threads_move.html):
What the heck did you do with the movable interface?! ;-)
-Howard
PS: Congrats on the nice job on shmem.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk