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, giovannibajo@libero.it, nobody@gcc.gnu.org Subject: Re: c++/10449: [3.4][New parser] Totally bogus error message on missing typename Date: Tue, 22 Apr 2003 23:00:00 -0000 [thread overview] Message-ID: <20030422230043.32209.qmail@sources.redhat.com> (raw) Synopsis: [3.4][New parser] Totally bogus error message on missing typename State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue Apr 22 23:00:42 2003 State-Changed-Why: I think the message is actually not so unclear: you try to call return Identity<T>::type(t); Since you don't have the missing "typename" here, the compiler assumes that Identity<T>::type is either a member function of Identity<T>, or a pointer-to-function. The argument is Foo&, so that's why you get error: no match for call to `(Foo) (Foo&)' since Identity::type is actually "Foo". So I guess the only complaint could be that the compiler shouldn't expand the typedef (that it shouldn't see here, after all), and rather print something like error: no match for call to `Identity<T>::type(Foo&)' But then, this wouldn't be much clearer either. I think the only thing we could do is to check if we such a match cannot be found, whether there's a type of that name and then issue a "missing typename?" message. But that would amount to re-inventing the implicit typename machinery, which we just got rid of. I leave it to the experts to decide what to do here... W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10449
reply other threads:[~2003-04-22 23:00 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=20030422230043.32209.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=giovannibajo@libero.it \ --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).