public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "widman at gimpel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/27732] Parentheses elicit spurious error: "missing '>' to terminate the template argument list" Date: Tue, 23 May 2006 15:10:00 -0000 [thread overview] Message-ID: <20060523151033.21398.qmail@sourceware.org> (raw) In-Reply-To: <bug-27732-10061@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from widman at gimpel dot com 2006-05-23 15:10 ------- By the way: whoever tackles this may also want to take a look at: template< int* p> struct A { }; template<> struct A<(int*)0>; ...which was made permissible by the recently-adopted wording that was proposed for Defect Report 354: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2006/n1998.html#354 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27732
next prev parent reply other threads:[~2006-05-23 15:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-22 20:08 [Bug c++/27732] New: " widman at gimpel dot com 2006-05-22 22:46 ` [Bug c++/27732] " bangerth at dealii dot org 2006-05-23 15:10 ` widman at gimpel dot com [this message] 2006-09-17 19:30 ` [Bug c++/27732] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-10-16 23:25 ` [Bug c++/27732] [4.0 " mmitchel at gcc dot gnu dot org 2007-02-03 17:22 ` gdr 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=20060523151033.21398.qmail@sourceware.org \ --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).