Title
Vague Wording for condition_variable_any
Status
c++14
Section
[thread.condition.condvarany]
Submitter
Pete Becker

Created on 2011-10-20.00:00:00 last changed 122 months ago

Messages

Date: 2013-04-19.22:22:17

Proposed resolution:

This wording is relative to N3337.

  1. Change [thread.timedmutex.requirements]/4 as indicated:

    condition_variable_any();
    

    […]

    -4- Error conditions:

    • resource_unavailable_try_againif any native handle type manipulated is not available if some non-memory resource limitation prevents initialization.
    • operation_not_permitted — if the thread does not have the privilege to perform the operation.
Date: 2013-04-20.00:00:00

[ 2013-04-20 Bristol ]

Date: 2012-10-19.07:50:57

[ 2012, Portland ]

Concurrency move to Ready.

Date: 2012-02-13.21:55:45

[ 2012, Kona ]

Copy the corresponding wording from the condition_variable constructor in [thread.condition.condvar] p4.

Move to Review.

Date: 2011-10-20.00:00:00

[thread.condition.condvarany]/4 says, in part, that condition_variable_any() throws an exception "if any native handle type manipulated is not available".

I don't know what that means. Is this intended to say something different from the analogous words for condition_variable() [[thread.condition.condvar]/4], "if some non-memory resource limitation prevents initialization"? If not, it should be worded the same way.

History
Date User Action Args
2014-02-20 13:20:35adminsetstatus: wp -> c++14
2013-04-25 19:07:07adminsetstatus: voting -> wp
2013-04-19 22:22:17adminsetmessages: + msg6471
2013-04-19 22:22:17adminsetstatus: ready -> voting
2012-10-19 07:50:57adminsetmessages: + msg6182
2012-10-19 07:50:57adminsetstatus: review -> ready
2012-02-13 21:55:45adminsetmessages: + msg6016
2012-02-13 21:55:45adminsetmessages: + msg6015
2012-02-13 21:55:45adminsetstatus: new -> review
2011-10-20 00:00:00admincreate