public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pubby.8 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51203] New: Recursive alias templates not working Date: Fri, 18 Nov 2011 07:49:00 -0000 [thread overview] Message-ID: <bug-51203-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51203 Bug #: 51203 Summary: Recursive alias templates not working Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: pubby.8@gmail.com -std=c++11 gcc version 4.7.0 20111112 (experimental) (GCC) I presume this is correctly formed code: template <typename t> struct foo { template <int n> using next = typename foo<t>::next<n + 1>; }; main.cpp:4:37: error: expected ‘;’ before ‘<’ token main.cpp:4:37: error: expected unqualified-id before ‘<’ token Interestingly, changing the line to this compiles so long as next isn't used: using next = typename foo<t>::next; The error is very similar to this ill-formed code: using next<n> = int; main.cpp:4:13: error: expected ‘=’ before ‘<’ token main.cpp:4:13: error: expected type-specifier before ‘<’ token main.cpp:4:13: error: expected ‘;’ before ‘<’ token main.cpp:4:13: error: expected unqualified-id before ‘<’ token
next reply other threads:[~2011-11-18 7:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-18 7:49 pubby.8 at gmail dot com [this message] 2011-11-18 8:22 ` [Bug c++/51203] " pubby.8 at gmail dot com 2011-11-18 8:27 ` [Bug c++/51203] Recursive alias template specialization causes compiler segfault pubby.8 at gmail dot com 2011-11-18 19:17 ` [Bug c++/51203] [C++0x] " daniel.kruegler at googlemail dot com 2011-11-25 13:28 ` dodji 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-51203-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).