Created on 2010-08-25.00:00:00 last changed 154 months ago
Proposed resolution:
Change [uncaught] p. 1 as follows:
Returns: true after the current thread has initialized initializing
an exception object (15.1) until a handler for the exception (including unexpected() or terminate())
is activated (15.3). [ Note: This includes stack unwinding (15.2). — end note ]
[ Adopted at 2010-11 Batavia ]
[ 2010 Batavia Concurrency group provides a Proposed Resolution ]
[ Resolution proposed by ballot comment ]
Update this clause to support safe calls from multiple threads without placing synchronization requirements on the user.
Addresses GB-73
The thread safety std::uncaught_exception() and the result of the function when multiple threads throw exceptions at the same time are unspecified. To make the function safe to use in the presence of exceptions in multiple threads the specification needs to be updated.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-08-23 20:07:26 | admin | set | status: wp -> c++11 |
| 2010-11-24 14:01:03 | admin | set | messages: + msg5428 |
| 2010-11-14 13:10:57 | admin | set | status: voting -> wp |
| 2010-11-13 01:17:02 | admin | set | status: open -> voting |
| 2010-11-13 01:11:40 | admin | set | status: immediate -> open |
| 2010-11-11 22:36:53 | admin | set | messages: + msg5342 |
| 2010-11-11 22:36:53 | admin | set | messages: + msg5341 |
| 2010-11-11 22:36:53 | admin | set | status: open -> immediate |
| 2010-10-24 22:33:31 | admin | set | messages: + msg5072 |
| 2010-10-24 03:04:13 | admin | set | messages: + msg4897 |
| 2010-08-25 00:00:00 | admin | create | |