Title
Various threading bugs #10
Status
c++11
Section
[thread.mutex.requirements]
Submitter
Pete Becker

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

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Change [thread.mutex.requirements] Mutex requirements, paragraph 4 as indicated:

-4- Error conditions: The error conditions for error codes, if any, reported by member functions of Mutex type shall be:

  • not_enough_memory — if there is not enough memory to construct the mutex object.
  • resource_unavailable_try_again — if any native handle type manipulated is not available.
  • operation_not_permitted — if the thread does not have the necessary permission to change the state of the mutex object.
  • device_or_resource_busy — if any native handle type manipulated is already locked.
  • invalid_argument — if any native handle type manipulated as part of mutex construction is incorrect.
Date: 2010-10-21.18:28:33

[ 2009-10 Santa Cruz: ]

Move to Ready. Fix the proposed wording with "functions of type Mutex" -> "functions of Mutex type"

Date: 2010-10-21.18:28:33

[ Beman provided proposed wording. ]

Date: 2010-10-21.18:28:33

[ Summit: ]

Move to open.

Date: 2009-01-07.00:00:00

[thread.mutex.requirements]: paragraph 4 is entitled "Error conditions", but according to [structure.specifications], "Error conditions:" specifies "the error conditions for error codes reported by the function." It's not clear what this should mean when there is no function in sight.

History
Date User Action Args
2011-08-23 20:07:26adminsetstatus: wp -> c++11
2010-10-21 18:28:33adminsetmessages: + msg4573
2010-10-21 18:28:33adminsetmessages: + msg4572
2010-10-21 18:28:33adminsetmessages: + msg4571
2010-10-21 18:28:33adminsetmessages: + msg4570
2009-01-07 00:00:00admincreate