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

### 70. Uncaught_exception() missing throw() specification

Section: 17.10 [support.exception], 99 [uncaught] Status: TC1 Submitter: Steve Clamage Opened: 1998-08-03 Last modified: 2016-01-28

Priority: Not Prioritized

View all other issues in [support.exception].

View all issues with TC1 status.

Discussion:

In article 3E04@pratique.fr, Valentin Bonnard writes:

uncaught_exception() doesn't have a throw specification.

It is intentional ? Does it means that one should be prepared to handle exceptions thrown from uncaught_exception() ?

uncaught_exception() is called in exception handling contexts where exception safety is very important.

Proposed resolution:

In 14.6.3 [except.uncaught], paragraph 1, 17.10 [support.exception], and 99 [uncaught], add "throw()" to uncaught_exception().