public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9460: parse error on template member function Date: Tue, 28 Jan 2003 21:16:00 -0000 [thread overview] Message-ID: <20030128211600.15871.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9460; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Oliver Schoenborn <oliver.schoenborn@utoronto.ca> Cc: gcc-gnats@gcc.gnu.org, <farfetchd@libero.it> Subject: Re: c++/9460: parse error on template member function Date: Tue, 28 Jan 2003 15:14:57 -0600 (CST) On Tue, 28 Jan 2003, Oliver Schoenborn wrote: > OK for the section, BUT there is still a bug, just not the right category > (like another developer said): when the member function name is changed from > test2 to test, the parse error disappears a few lines above disappears. This > has to be re-opened and re-categorized. No, Giovanni is wrong: both examples he shows are perfectly legal: in the first one, Foo::F1 is called as can easily be seen in the assembler output. The fact the Bar::F1 exists has no influence whatsoever. In the second, the same obviously holds. In both cases, you don't need the "template" keyword for disambiguation, since neither the expression before the "." is template dependent (it is just an object of non-templated type "Foo"), nor the one after the dot, which _is_ templates by the template type is known at the time of parsing, being a constant "int". It would be different if you would call Foo().F1<A> (); in which case you would have to use Foo().template F1<A> (); Unfortunately, this ICEs with the present mainline compile (I just filed a report for this). W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-01-28 21:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-28 21:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-29 15:46 Wolfgang Bangerth 2003-01-29 9:16 Giovanni Bajo 2003-01-28 21:16 Wolfgang Bangerth 2003-01-28 2:36 Farfetch'd 2003-01-27 19:55 bangerth 2003-01-27 19:26 oliver.schoenborn
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=20030128211600.15871.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).