public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/16582] New: Wrong diagnostic when using "&a[1]" as template argument Date: Fri, 16 Jul 2004 01:57:00 -0000 [thread overview] Message-ID: <20040716015746.16582.giovannibajo@libero.it> (raw) Compiling the following code: ----------------------------------------- template<class T, char* p> struct X { X(); X(const char* q) { /* ... */ } }; char p[] = "Vivisectionist"; X<int, p> x2; // OK X<int, &p[0]> x3; // ERROR ----------------------------------------- I get this error on mainline: nontype1.cc: At global scope: nontype1.cc:8: error: missing `>' to terminate the template argument list nontype1.cc:8: error: template argument 2 is invalid nontype1.cc:8: error: expected init-declarator before '>' token nontype1.cc:8: error: expected `,' or `;' before '>' token The message is totally bogus. The real problem is that a call to operator[] is not be allowed within a template argument. This happens with both 3.4 and mainline. Not a regression though since older versions even incorrectly accepted the code (in fact, I fixed this very issue within the new parser). -- Summary: Wrong diagnostic when using "&a[1]" as template argument Product: gcc Version: 3.5.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: giovannibajo at libero dot it CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16582
next reply other threads:[~2004-07-16 1:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-16 1:57 giovannibajo at libero dot it [this message] 2004-07-16 3:36 ` [Bug c++/16582] " bangerth at dealii dot org 2004-07-16 6:50 ` pinskia at gcc dot gnu dot 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=20040716015746.16582.giovannibajo@libero.it \ --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).