public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8222: [parser] call of member template inside template function
Date: Thu, 01 May 2003 14:46:00 -0000	[thread overview]
Message-ID: <20030501144601.26234.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

The following reply was made to PR c++/8222; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<setzersn@gmx.de>
Cc:  
Subject: Re: c++/8222: [parser] call of member template inside template function
Date: Thu, 1 May 2003 16:38:12 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8222
 
 Reduced snippet:
 
 ---------------------------
 struct Foo
 {
     template <class>
     void func() {}
 };
 
 template <class>
 void Bar(Foo* p)
 {
     p->func<int>();
 }
 
 int main()
 {
     Foo c;
     Bar<int>(&c);
 }
 ---------------------------
 pr8222.cpp: In function `void Bar(Foo*)':
 pr8222.cpp:10: error: expected primary-expression
 pr8222.cpp:10: error: expected `;'
 
 The obvious workaround is to put the template keyword before func, as in
 "p->template func<int>()". But §14.2p3 [temp.names] specifies that the
 keyword is compulsory only if the postfix-expression is dependent, which is
 not the case in the above snippet. So the above code is legal and should not
 be rejected. This might be a duplicate though, I think I saw a similar
 report somewhere.
 
 Confirmed on every GCC up to mainline 20030430.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-05-01 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 14:46 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23  5:51 lerdsuwa

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=20030501144601.26234.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --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).