public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ayg at aryeh dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54043] [C++0x] cout << nullptr does not work
Date: Fri, 20 Jul 2012 12:39:00 -0000	[thread overview]
Message-ID: <bug-54043-4-bR8mkcLECE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54043-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54043

--- Comment #5 from Aryeh Gregor <ayg at aryeh dot name> 2012-07-20 12:39:00 UTC ---
Thanks.  Is there any publicly-accessible summary of the previous discussion,
so that I can read it and not retread old ground?  Also, if the WG agrees to
make the change in the next version, would gcc be willing to implement it right
away rather than waiting for the next version of the standard to actually be
released?  (I'm assuming yes, since there was a bunch of C++0x stuff
implemented before it was actually released.)


  parent reply	other threads:[~2012-07-20 12:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  8:46 [Bug c++/54043] New: " ayg at aryeh dot name
2012-07-20 10:21 ` [Bug c++/54043] " redi at gcc dot gnu.org
2012-07-20 12:01 ` ayg at aryeh dot name
2012-07-20 12:05 ` redi at gcc dot gnu.org
2012-07-20 12:18 ` redi at gcc dot gnu.org
2012-07-20 12:39 ` ayg at aryeh dot name [this message]
2012-07-20 12:46 ` [Bug c++/54043] [C++11] " redi at gcc dot gnu.org
2012-07-20 13:59 ` daniel.kruegler at googlemail dot com
2012-07-20 14:04 ` daniel.kruegler at googlemail dot com
2012-07-20 14:14 ` redi at gcc dot gnu.org
2012-07-20 19:02 ` daniel.kruegler at googlemail dot com
2012-07-23 11:00 ` ayg at aryeh dot name
2013-03-04 10:45 ` [Bug libstdc++/54043] " paolo.carlini at oracle dot com
2013-03-04 10:47 ` daniel.kruegler at googlemail dot com
2013-03-04 10:50 ` [Bug libstdc++/54043] [LWG 2221] " paolo.carlini at oracle dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-54043-4-bR8mkcLECE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).