This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/3086: [2003-01-02]Suggested extension to a template related warning.
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, whitley at bangpath dot org
- Date: 8 May 2003 21:49:11 -0000
- Subject: Re: c++/3086: [2003-01-02]Suggested extension to a template related warning.
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, whitley at bangpath dot org, gcc-gnats at gcc dot gnu dot org
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