public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: bangerth@ticam.utexas.edu, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/10244: [3.4 regression] In error messages for templates, template type is no longer displayed
Date: Tue, 29 Apr 2003 20:46:00 -0000 [thread overview]
Message-ID: <20030429204605.14503.qmail@sources.redhat.com> (raw)
Synopsis: [3.4 regression] In error messages for templates, template type is no longer displayed
State-Changed-From-To: open->closed
State-Changed-By: reichelt
State-Changed-When: Tue Apr 29 20:46:04 2003
State-Changed-Why:
Not a bug, IMHO.
It's a consequence of improved two-stage name-lookup.
Since BOGUS is not a dependant name, the parser can see that this is a bug,
while parsing the template (a not while instantiating it). As you can see,
not only the "[with T = int]" is missing, but also the
"compiler_bug.cc:9: instantiated from here" line. There is in fact no
value for T when the error message is issued.
On the other hand, if I change the code to
------------------------------------------
template <class T> void f(T) { T::BOGUS; }
int main() { f (1); }
------------------------------------------
the compiler has to wait for the instantiation to be able to see that
BOGUS is really bogus. In this case I get:
bogus.cc: In function `void f(T) [with T = int]':
bogus.cc:2: instantiated from here
bogus.cc:1: error: `int' is not an aggregate type
which does make sense to me.
Regards,
Volker
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10244
next reply other threads:[~2003-04-29 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 20:46 reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-27 17:06 bangerth
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=20030429204605.14503.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--cc=bangerth@ticam.utexas.edu \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--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: link
Be 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).