public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9154: [3.4 regression] [diagnostic] poor error message for ">>" vs. "> >" for nested template args Date: Mon, 05 May 2003 00:16:00 -0000 [thread overview] Message-ID: <20030505001600.9946.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9154; it has been noted by GNATS. From: "Giovanni Bajo" <giovannibajo@libero.it> To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <tilps@hotmail.com>, <gcc-prs@gcc.gnu.org> Cc: Subject: Re: c++/9154: [3.4 regression] [diagnostic] poor error message for ">>" vs. "> >" for nested template args Date: Mon, 5 May 2003 02:06:22 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9154 For reference, Comeau gives: "pr9154.cpp", line 6: error: space required between adjacent ">" delimiters of nested template argument lists (">>" is the right shift operator) a<a<int>> blah; ^ Giovanni Bajo
next reply other threads:[~2003-05-05 0:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-05 0:16 Giovanni Bajo [this message] 2003-05-09 19:03 giovannibajo
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=20030505001600.9946.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).