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++/52315] [C++11] constexpr object of nested class Date: Mon, 20 Feb 2012 23:00:00 -0000 [thread overview] Message-ID: <bug-52315-4-9KTEM2WRb9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52315-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52315 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> 2012-02-20 22:44:01 UTC --- 3.3.7: 1) The potential scope of a name declared in a class consists not only of the declarative region following the name’s point of declaration, but also of all function bodies, brace-or-equal-initializers of non-static data members, and default arguments in that class (including such things in nested classes). So within B::value, A::stuff is in scope, so we need to wait until A is complete to parse B::value, so B::value can't be used in constant expressions in A.
next prev parent reply other threads:[~2012-02-20 22:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-20 11:05 [Bug c++/52315] New: " oleg.endo@t-online.de 2012-02-20 13:43 ` [Bug c++/52315] " daniel.kruegler at googlemail dot com 2012-02-20 15:08 ` redi at gcc dot gnu.org 2012-02-20 23:00 ` jason at gcc dot gnu.org [this message] 2012-02-20 23:35 ` jakub at gcc dot gnu.org 2012-03-13 11:30 ` 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-52315-4-9KTEM2WRb9@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).