public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "edward.schere@trash-mail.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50108] New: [C++0x] Variadic templates with both type and non-type parameters Date: Wed, 17 Aug 2011 14:38:00 -0000 [thread overview] Message-ID: <bug-50108-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50108 Bug #: 50108 Summary: [C++0x] Variadic templates with both type and non-type parameters Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: edward.schere@trash-mail.com I'm not quite sure if this is a GCC bug, because the current C++ draft version is unclear about this. I found neither an example that this code is ill-formed, nor did I found an example that it's ok: template<int... Ints, typename... Types> class test_template { }; int main() { test_template<1,2,3,int,double> tt; return 0; } GCC 4.6.1 rejects this code with the error "parameter pack 'Ints' must be at the end of the template parameter list". I guess the code is well-formed, because it is unambiguous and (semantically) identical with the following code (that works fine in GCC): template<int Int0, typename... Types> class test_template { }; template<int Int0, int Int1, typename... Types> class test_template { }; template<int Int0, int Int1, int Int2, typename... Types> class test_template { };
next reply other threads:[~2011-08-17 14:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-17 14:38 edward.schere@trash-mail.com [this message] 2011-08-17 15:27 ` [Bug c++/50108] " redi at gcc dot gnu.org 2011-09-23 11:28 ` 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-50108-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).