This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofC++11 status.
Section: 32.6.4[thread.mutex.requirements]Status:C++11Submitter: Pete BeckerOpened: 2009-01-07Last modified: 2016-01-28
Priority:Not Prioritized
View otheractive issues in [thread.mutex.requirements].
View all otherissues in [thread.mutex.requirements].
View all issues withC++11 status.
Discussion:
32.6.4[thread.mutex.requirements]: paragraph 4 is entitled"Error conditions", but according to 16.3.2.4[structure.specifications], "Errorconditions:" specifies "the error conditions for error codes reported bythe function." It's not clear what this should mean when there is nofunction in sight.
[Summit:]
Move to open.
[Beman provided proposed wording.]
[2009-10 Santa Cruz:]
Move to Ready. Fix the proposed wording with "functions of type Mutex"-> "functions of Mutex type"
Proposed resolution:
Change 32.6.4[thread.mutex.requirements] Mutex requirements,paragraph 4 as indicated:
-4-
Error conditions:The error conditions for error codes, if any, reported by memberfunctions of Mutex type shall be:
not_enough_memory— if there is not enough memory to constructthe mutex object.resource_unavailable_try_again— if any native handle typemanipulated is not available.operation_not_permitted— if the thread does not have thenecessary permission to change the state of the mutex object.device_or_resource_busy— if any native handle typemanipulated is already locked.invalid_argument— if any native handle type manipulated aspart of mutex construction is incorrect.