public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, whitley@bangpath.org Subject: Re: c++/3086: [2003-01-02]Suggested extension to a template related warning. Date: Thu, 08 May 2003 21:49:00 -0000 [thread overview] Message-ID: <20030508214911.23131.qmail@sources.redhat.com> (raw) Synopsis: [2003-01-02]Suggested extension to a template related warning. State-Changed-From-To: suspended->closed State-Changed-By: bangerth State-Changed-When: Thu May 8 21:49:11 2003 State-Changed-Why: In this particular case, I think there's not much we can do. Your code looks like this: --------------- static const int FOO = 5; Handle<MyPrivateData<FOO>> handle(pd); ---------------------- So FOO is an integer, and the token >> would be valid after that if "handle" were another valid integer. Gcc tries some second guessing, in that it assumes that handle is just undefined, and it proposes this in its error message, but the problem is somewhere else. I think in this case every other solution is just as good or bad as the present state. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3086
reply other threads:[~2003-05-08 21:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030508214911.23131.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=whitley@bangpath.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).