Created on 2012-10-17.00:00:00 last changed 121 months ago
[Moved to DR at the September, 2013 meeting.]
Proposed resolution (April, 2013):
Change _N4885_6.7.5.5.4 [basic.stc.dynamic.safety] paragraph 4 as follows:
Alternatively, an implementation may have strict pointer safety, in which case a pointer value referring to an object with dynamic storage duration that is not a safely-derived pointer value is an invalid pointer value unless the referenced complete objectis of dynamic storage duration andhas previously been declared reachable (_N4885_.20.10.5 [util.dynamic.safety]). [Note:...
According to _N4885_6.7.5.5.4 [basic.stc.dynamic.safety] paragraph 4,
an implementation may have strict pointer safety, in which case a pointer value that is not a safely-derived pointer value is an invalid pointer value unless the referenced complete object is of dynamic storage duration and has previously been declared reachable (_N4885_.20.10.5 [util.dynamic.safety]).
“Safely-derived pointer” is defined only with respect to dynamically-allocated storage. Presumably pointers to objects with automatic and static storage duration should also be considered valid.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-11-24 00:00:00 | admin | set | status: drwp -> c++14 |
| 2014-03-03 00:00:00 | admin | set | status: dr -> drwp |
| 2013-10-14 00:00:00 | admin | set | messages: + msg4680 |
| 2013-10-14 00:00:00 | admin | set | status: ready -> dr |
| 2013-05-03 00:00:00 | admin | set | messages: + msg4306 |
| 2013-05-03 00:00:00 | admin | set | status: open -> ready |
| 2012-10-17 00:00:00 | admin | create | |