Created on 2009-01-07.00:00:00 last changed 162 months ago
Proposed resolution:
Change [thread.condition.condvar] p3:
- ...
device_or_resource_busy -- if attempting to initialize a previously-initialized but as of yet undestroyed condition_variable.
[ Batavia (2009-05): ]
We agree with the proposed resolution. Move to Tentatively Ready.
[ Summit: ]
Move to review. Proposed resolution: strike the device_or_resource_busy error condition from the constructor of condition_variable.
- This is a POSIX error that cannot occur in this interface because the C++ interface does not separate declaration from initialization.
[thread.condition.condvar]: the constructor for condition_variable throws an exception with error code device_or_resource_busy "if attempting to initialize a previously-initialized but as of yet undestroyed condition_variable." How can this occur?
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-08-23 20:07:26 | admin | set | status: wp -> c++11 |
| 2010-10-21 18:28:33 | admin | set | messages: + msg4599 |
| 2010-10-21 18:28:33 | admin | set | messages: + msg4598 |
| 2010-10-21 18:28:33 | admin | set | messages: + msg4597 |
| 2009-01-07 00:00:00 | admin | create | |