public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50563] [C++0x] Weird syntax acceptance rules for non-static data members initialized in place Date: Thu, 13 Oct 2011 21:51:00 -0000 [thread overview] Message-ID: <bug-50563-4-o18PRquoD7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50563-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50563 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2011-10-13 AssignedTo|unassigned at gcc dot |jason at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1
next prev parent reply other threads:[~2011-10-13 21:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-29 8:19 [Bug c++/50563] New: Weird syntax acceptance rules for non-static data members initialized in place (C++0x) ethouris at gmail dot com 2011-09-29 8:20 ` [Bug c++/50563] " redi at gcc dot gnu.org 2011-10-09 9:16 ` [Bug c++/50563] [C++0x] Weird syntax acceptance rules for non-static data members initialized in place paolo.carlini at oracle dot com 2011-10-13 21:51 ` jason at gcc dot gnu.org [this message] 2011-10-14 19:13 ` jason at gcc dot gnu.org 2011-10-14 19:22 ` jason at gcc dot gnu.org
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-50563-4-o18PRquoD7@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: linkBe 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).