- Title
- Requirements for exceptions thrown by allocation functions
- Status
- cd1
- Section
- 6.8.6.5.2 [basic.stc.dynamic.allocation]
- Submitter
- Alisdair Meredith
Created on 2005-05-22.00:00:00 last changed 217 months ago
Messages
Date: 2006-10-15.00:00:00
[Voted into WP at the October, 2006 meeting.]
Date: 2006-04-15.00:00:00
Proposed resolution (April, 2006): Change the last sentence of 6.8.6.5.2 [basic.stc.dynamic.allocation] paragraph 3
as indicated:
Any other allocation function that fails to allocate storage shall
only indicate failure only by throwing an exception of
class std::bad_alloc (17.6.4.1 [bad.alloc]) or a
class derived from std::bad_alloc a type that would
match a handler (14.4 [except.handle]) of type
std::bad_alloc (17.6.4.1 [bad.alloc]).
Date: 2026-07-25.21:52:10
According to 6.8.6.5.2 [basic.stc.dynamic.allocation] paragraph 3, Shouldn't this statement have the usual requirements for an
unambiguous and accessible base class?
Any other allocation function that fails to allocate storage shall
only indicate failure by throwing an exception of
class std::bad_alloc (17.6.4.1 [bad.alloc]) or a
class derived from std::bad_alloc .
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-10-05 00:00:00 | admin | set | status: wp -> cd1 |
| 2007-05-06 00:00:00 | admin | set | status: dr -> wp |
| 2006-11-05 00:00:00 | admin | set | messages: + msg1430 |
| 2006-11-05 00:00:00 | admin | set | status: ready -> dr |
| 2006-04-22 00:00:00 | admin | set | status: review -> ready |
| 2005-10-22 00:00:00 | admin | set | messages: + msg1230 |
| 2005-10-22 00:00:00 | admin | set | status: open -> review |
| 2005-05-22 00:00:00 | admin | create | |