|
Boost :
|
- Next message: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- In reply to: Zach Laine: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Zach Laine: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
On Aug 21, 2007, at 4:41 PM, Zach Laine wrote:
> Are there any plan to add transfer_lock, and any other such generic
> algoirthms you have lying around, to the proposal as well?
Thanks for the great comments Zach. owns_mutex() or some other
suggestion sounds fine to me too.
I put transfer_lock into <shared_mutex> which is TR2-targeted. The
std::lock and std::try_lock algorithms are in <mutex>, actually in the
implementation <mutex_base> header, and targeted towards C++0X. Some
of the other examples are just meant to be example client code (like
mutex_debug). If you have a burning desire to get one of them into C+
+0X or TR2, please let me know.
-Howard
- Next message: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- In reply to: Zach Laine: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Peter Dimov: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Zach Laine: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk