This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++11 status.
Section: 32.7.4 [thread.condition.condvar] Status: C++11 Submitter: Pete Becker Opened: 2009-01-07 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [thread.condition.condvar].
View all issues with C++11 status.
Discussion:
32.7.4 [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?
[ Summit: ]
Move to review. Proposed resolution: strike the
device_or_resource_busyerror condition from the constructor ofcondition_variable.
- This is a POSIX error that cannot occur in this interface because the C++ interface does not separate declaration from initialization.
[ Batavia (2009-05): ]
We agree with the proposed resolution. Move to Tentatively Ready.
Proposed resolution:
Change 32.7.4 [thread.condition.condvar] p3:
- ...
device_or_resource_busy-- if attempting to initialize a previously-initialized but as of yet undestroyedcondition_variable.