Created on 2009-12-03.00:00:00 last changed 96 months ago
[Voted into the WP at the November, 2010 meeting.]
Proposed resolution (October, 2010):
Change 7.3.12 [conv.ptr] paragraph 1 as follows:
...A null pointer constant can be converted to a pointer type; the result is the null pointer value of that type and is distinguishable from every other value of pointer to object or pointer to function type. Two null pointer values...
Change 7.3.13 [conv.mem] paragraph 1 as follows:
A null pointer constant (7.3.12 [conv.ptr]) can be converted to a pointer to member type; the result is the null member pointer value of that type and is distinguishable from any pointer to member not created from a null pointer constant. Two null member pointer values...
Change 220.127.116.11 [expr.static.cast] paragraph 7 as follows:
The inverse of any standard conversion sequence (Clause 7.3 [conv])
, other than thelvalue-to-rvalue (7.3.2 [conv.lval]), array-to-pointer (7.3.3 [conv.array]), function-to-pointer (7.3.4 [conv.func]), andboolean (7.3.14 [conv.fctptr]) conversion s, can be performed explicitly using static_cast. A program is ill-formed...
According to 18.104.22.168 [expr.static.cast] paragraph 7, static_cast can be used to perform the inverse of any standard conversion sequence except the lvalue-to-rvalue, array-to-pointer, function-to-pointer, and boolean conversions. The null pointer and null pointer-to-member conversions should also be listed — it should not be permitted to cast a pointer or pointer-to-member to either integral type or std::nullptr_t.
|2014-03-03 00:00:00||admin||set||status: fdis -> c++11|
|2011-04-10 00:00:00||admin||set||status: dr -> fdis|
|2010-11-29 00:00:00||admin||set||messages: + msg3154|
|2010-11-29 00:00:00||admin||set||status: tentatively ready -> dr|
|2010-10-18 00:00:00||admin||set||messages: + msg2975|
|2010-10-18 00:00:00||admin||set||status: drafting -> tentatively ready|
|2010-08-23 00:00:00||admin||set||status: open -> drafting|