|
Boost :
|
- Next message: Yuval Ronen: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: Jens Finkhäuser: "Re: [boost] How to claim copyright (and potentially claim prior art?)"
- In reply to: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Yuval Ronen: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Yuval Ronen: "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"
Howard Hinnant wrote:
> Vendor C, with the best of intentions, decides that the release build
> of the std::lib should contain this checking (std::lib vendors
> including debug checks in release builds should sound familiar to many
> of you). Now we have goal #3, but have lost goal #1, and there is no
> wrapper we can use to get it back.
>
> How do we prevent, or at least discourage, Vendor C from taking this
> path?
Shouldn't Vendor C be allowed this freedom? If its customers prefer paying
the price of a pointer in exchange for the ever-present checks, why should
the vendor be prevented from delivering the product they want? We can
explain the rationale for the design and our suggested implementation in
non-normative notes and let the vendors make the informed decision.
- Next message: Yuval Ronen: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Previous message: Jens Finkhäuser: "Re: [boost] How to claim copyright (and potentially claim prior art?)"
- In reply to: Howard Hinnant: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Next in thread: Yuval Ronen: "Re: [boost] [thread] RFC standard proposed mutex, read-write mutex, condition"
- Reply: Yuval Ronen: "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"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk