public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60786] New: In C++11 an explicit instantiation with an unqualified name must be in the right namespace Date: Tue, 08 Apr 2014 12:20:00 -0000 [thread overview] Message-ID: <bug-60786-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60786 Bug ID: 60786 Summary: In C++11 an explicit instantiation with an unqualified name must be in the right namespace Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org This should not be accepted in C++11 mode: namespace A { template<typename T> struct B { }; } using A::B; template class B<int>; [temp.explicit] p3: "An explicit instantiation shall appear in an enclosing namespace of its template. If the name declared in the explicit instantiation is an unqualified name, the explicit instantiation shall appear in the namespace where its template is declared or, if that namespace is inline (7.3.1), any namespace from its enclosing namespace set." This is a change from C++03: "A definition of a class template or class member template shall be in scope at the point of the explicit instantiation of the class template or class member template."
next reply other threads:[~2014-04-08 12:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-08 12:20 redi at gcc dot gnu.org [this message] 2014-04-15 19:06 ` [Bug c++/60786] " redi at gcc dot gnu.org 2014-04-15 19:08 ` redi at gcc dot gnu.org 2014-12-14 15:37 ` ville.voutilainen at gmail dot com 2021-08-04 20:42 ` pinskia 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-60786-4@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).