Issue 964 - WG21 LWG Issues
Title
Various threading bugs #14
Status
resolved
Section
[thread.condition.condvarany]
Submitter
Pete Becker

Created on 2009-01-07.00:00:00 last changed 159 months ago

Messages

msg5693 (view)
Date: 2011-04-30.23:09:42

Proposed resolution:

Resolved 2011-03 Madrid meeting by paper N3278

msg4595 (view)
Date: 2010-10-25.22:40:06

[ 2010 Pittsburgh: ]

We don't have throw clauses for condition variables.

This issue may be dependent on LWG 1268.

Leave open. Detlef will coordinate with Benjamin.

Consider merging LWG 964, 966, and 1268 into a single paper.

msg4594 (view)
Date: 2010-10-21.18:28:33

[ 2009-10 Santa Cruz: ]

Leave open. Benjamin to provide wording.

msg4593 (view)
Date: 2010-10-21.18:28:33

[ Post Summit Howard adds: ]

The original intention (N2447) was to let the OS return whatever errors it was going to return, and for those to be translated into exceptions, for both condition_variable and condition_variable_any. I have not received any complaints about specific error conditions from vendors on non-POSIX platforms, but such complaints would not surprise me if they surfaced.

msg4592 (view)
Date: 2010-10-21.18:28:33

[ Summit: ]

Move to open, pass to Howard. If this is intentional, a note may be helpful. If the error conditions are to be copied from condition_variable, this depends on LWG 965.

msg4591 (view)
Date: 2009-01-07.00:00:00

The requirements for the constructor for condition_variable has several error conditions, but the requirements for the constructor for condition_variable_any has none. Is this difference intentional?

History
Date User Action Args
2011-03-24 21:43:06adminsetmessages: + msg5693
2011-03-24 21:43:06adminsetstatus: open -> resolved
2010-10-21 18:28:33adminsetmessages: + msg4595
2010-10-21 18:28:33adminsetmessages: + msg4594
2010-10-21 18:28:33adminsetmessages: + msg4593
2010-10-21 18:28:33adminsetmessages: + msg4592
2009-01-07 00:00:00admincreate