This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/54043] [C++11] cout << nullptr does not work
- From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 20 Jul 2012 13:59:41 +0000
- Subject: [Bug c++/54043] [C++11] cout << nullptr does not work
- Auto-submitted: auto-generated
- References: <bug-54043-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54043
Daniel KrÃgler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler at
| |googlemail dot com
--- Comment #7 from Daniel KrÃgler <daniel.kruegler at googlemail dot com> 2012-07-20 13:59:41 UTC ---
In this context it is presumably interesting to mention a recently intended
core language change:
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1423
I believe this change will have effects on this issue: Once accepted, the
nullptr_t -> bool conversion will no longer be considered (I have not yet
checked whether there would still exist other conversion ambiguities).
Jonathan, given the state of 1423, should I open a new reminder bugzilla entry
to take care of this? AFAIK we have done so for other "ready" issues in the
past.