|
Boost :
|
- Next message: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: David Abrahams: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- In reply to: David Abrahams: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Howard Hinnant: "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"
On Aug 22, 2007, at 7:14 PM, David Abrahams wrote:
> The reason is, "Peter said so." In other words, if you accept Peter's
> modification, the contract says "if you construct it this way, it's a
> logic error to use it that way."
>
> I don't see a problem with that.
Ok, so what if Howard says: If you construct it this way, it's a run
time error to use it the that way. Is that statement in any way more
or less correct?
I fear we're arguing about the number of angles that can dance on the
head of a pin. We need use cases in this area and we have none (so
far).
-Howard
- Next message: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: David Abrahams: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- In reply to: David Abrahams: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Howard Hinnant: "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"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk