Created on2012-02-07.00:00:00 last changed145 months ago
[Moved to DR at the October, 2012 meeting.]
Proposed resolution (February, 2012):
Change 7.6.2.2 [expr.unary.op] paragraph 5 as follows:
The address of an object of incomplete type can be taken, but ifthe complete type of that object is a class type that declaresoperator&() as a member function, then the behavior isundefined (and no diagnostic is required).If& is applied to an lvalue of incomplete class type andthe complete type declaresoperator&(), it is unspecifiedwhether the operator has the built-in meaning or the operator functionis called. The operand of& shall not be abit-field.
According to 7.6.2.2 [expr.unary.op] paragraph 5,
The address of an object of incomplete type can be taken, but if thecomplete type of that object is a class type that declaresoperator&() as a member function, then the behavior isundefined (and no diagnostic is required).
This should actually be “ill-formed, no diagnosticrequired” instead of undefined behavior, since the problemcould be detected by whole-program analysis. Also, it's not clearwhat this means for constant expressions.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-03 00:00:00 | admin | set | status: drwp -> cd3 |
| 2013-05-03 00:00:00 | admin | set | status: dr -> drwp |
| 2012-11-03 00:00:00 | admin | set | messages: +msg4133 |
| 2012-11-03 00:00:00 | admin | set | status: ready -> dr |
| 2012-02-27 00:00:00 | admin | set | messages: +msg3703 |
| 2012-02-07 00:00:00 | admin | create | |