- Title
- Explicit destructor invocation and qualified-ids
- Status
- cd1
- Section
- 11.4.7 [class.dtor]
- Submitter
- Mike Miller
Created on 2001-02-22.00:00:00 last changed 208 months ago
Messages
Date: 2001-10-15.00:00:00
[Moved to DR at 10/01 meeting.]
Date: 2001-04-15.00:00:00
Proposed resolution (04/01):
Change 11.4.7 [class.dtor] paragraph 12 as follows:
[Note: an explicit destructor call must always be written using a member access operator (7.6.1.5 [expr.ref]) or a qualified-id (_N4567_.5.1.1 [expr.prim.general]); in particular, the unary-expression ~X() in a member function is not an explicit destructor call (7.6.2.2 [expr.unary.op]).]
Date: 2001-02-22.00:00:00
11.4.7 [class.dtor] paragraph 12 contains the following note:
an explicit destructor call must always be written using a member access operator (7.6.1.5 [expr.ref]); in particular, the unary-expression ~X() in a member function is not an explicit destructor call (7.6.2.2 [expr.unary.op]).
This note is incorrect, as an explicit destructor call can be written as a qualified-id, e.g., X::~X(), which does not use a member access operator.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-10-05 00:00:00 | admin | set | status: wp -> cd1 |
| 2003-04-25 00:00:00 | admin | set | status: dr -> wp |
| 2002-05-10 00:00:00 | admin | set | messages: + msg686 |
| 2001-11-09 00:00:00 | admin | set | status: ready -> dr |
| 2001-05-20 00:00:00 | admin | set | messages: + msg478 |
| 2001-05-20 00:00:00 | admin | set | status: open -> ready |
| 2001-02-22 00:00:00 | admin | create | |