Title
Bad footnote about explicit exception-specification
Status
resolved
Section
[res.on.exception.handling]
Submitter
Great Britain

Created on 2017-02-03.00:00:00 last changed 86 months ago

Messages

Date: 2017-02-21.20:53:12

Proposed resolution:

Resolved by accepting P0003R5.

Date: 2017-02-15.00:00:00

[ 2017-02-13, Alisdair comments ]

Just to confirm that issue 2867 was filed when it looked like the paper to remove exception specifications from the language had missed C++17. The very specific edit requested by the issue can be found in the paper P0003R5 that was applied.

I suggest we mark as resolved by the above paper, rather than "resolved editorially".

Date: 2017-02-15.00:00:00

[ 2017-02-03, Daniel comments ]

The referenced footnote had the following content in the ballot document N4604:

That is, an implementation may provide an explicit exception-specification that defines the subset of "any" exceptions thrown by that function. This implies that the implementation may list implementation-defined types in such an exception-specification.

In N4618 this footnote has already been removed, I therefore suggest to resolve the issue as "Resolved by editorial change".

Date: 2017-02-03.00:00:00

Addresses GB 40

The freedom referenced in footnote 189 was curtailed in C++11 to allow only non-throwing specifications. The footnote is both wrong, and unnecessary.

Proposed change:

Strike footnote 189.

History
Date User Action Args
2017-02-21 20:53:12adminsetmessages: + msg8969
2017-02-21 20:53:12adminsetstatus: new -> resolved
2017-02-19 16:16:11adminsetmessages: + msg8950
2017-02-03 19:23:20adminsetmessages: + msg8850
2017-02-03 00:00:00admincreate