This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.

### 2240. Probable misuse of term "function scope" in [thread.condition]

Section: 32.6.4 [thread.condition.condvar], 32.6.5 [thread.condition.condvarany] Status: Resolved Submitter: FrankHB1989 Opened: 2013-02-03 Last modified: 2016-01-28

Priority: Not Prioritized

View all other issues in [thread.condition.condvar].

View all issues with Resolved status.

Discussion:

All usages of "function scope" in 32.6.4 [thread.condition.condvar] and 32.6.5 [thread.condition.condvarany], such as 32.6.4 [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".

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

Proposed resolution:

Resolved by proposed resolution of LWG 2135.