|
Boost :
|
- Next message: Yuval Ronen: "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: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Zach Laine: "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"
Howard Hinnant wrote:
> Thanks for the great comments Zach. owns_mutex() or some other
> suggestion sounds fine to me too.
How about holds_lock? 'owns' doesn't quite ring true with me.
- Next message: Yuval Ronen: "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: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Zach Laine: "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