Title
Probable misuse of term "function scope" in [thread.condition]
Status
resolved
Section
[thread.condition.condvar] [thread.condition.condvarany]
Submitter
FrankHB1989

Created on 2013-02-03.00:00:00 last changed 131 months ago

Messages

Date: 2013-09-27.00:00:36

Proposed resolution:

Resolved by proposed resolution of LWG 2135.

Date: 2013-09-27.00:00:36

[ 2013-09 Chicago: Resolved by proposed resolution of LWG 2135 ]

Date: 2013-02-03.00:00:00

All usages of "function scope" in [thread.condition.condvar] and [thread.condition.condvarany], such as [thread.condition.condvar] p10 b4:

If the function exits via an exception, lock.lock() shall be called prior to exiting the function scope.

seem to be inappropriate compared to the actual core language definition of [basic.funscope]:

Labels (6.1) have function scope and may be used anywhere in the function in which they are declared. Only labels have function scope.

Probably the intended meaning is "outermost block scope of the function".

History
Date User Action Args
2014-02-27 17:03:20adminsetstatus: wp -> resolved
2014-02-20 13:52:38adminsetstatus: voting -> wp
2014-02-12 14:19:44adminsetstatus: ready -> voting
2013-09-27 00:25:00adminsetstatus: new -> ready
2013-09-27 00:00:36adminsetmessages: + msg6646
2013-09-27 00:00:36adminsetmessages: + msg6645
2013-02-03 00:00:00admincreate