This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofResolved status.
Section: 32.7.5[thread.condition.condvarany]Status:ResolvedSubmitter: Pete BeckerOpened: 2009-01-07Last modified: 2016-01-28
Priority:Not Prioritized
View all otherissues in [thread.condition.condvarany].
View all issues withResolved status.
Discussion:
The requirements for the constructor forcondition_variable has severalerror conditions, but the requirements for the constructor forcondition_variable_any has none. Is this difference intentional?
[Summit:]
Move to open, pass to Howard. If this is intentional, a note may behelpful. If the error conditions are to be copied from
condition_variable, this depends on LWG965(i).
[Post Summit Howard adds:]
The original intention (N2447)was to let the OS return whatever errors it was going to return, and forthose to be translated into exceptions, for both
condition_variableandcondition_variable_any. I have notreceived any complaints about specific error conditions from vendors onnon-POSIX platforms, but such complaints would not surprise me if they surfaced.
[2009-10 Santa Cruz:]
Leave open. Benjamin to provide wording.
[2010 Pittsburgh:]
We don't have throw clauses for condition variables.
This issue may be dependent on LWG1268(i).
Leave open. Detlef will coordinate with Benjamin.
Consider merging LWG 964,966(i), and1268(i) into asingle paper.
Proposed resolution:
Resolved 2011-03 Madrid meeting by paperN3278