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++/9460: parse error on template member function
Date: Wed, 29 Jan 2003 09:16:00 -0000	[thread overview]
Message-ID: <20030129091600.13674.qmail@sources.redhat.com> (raw)

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

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>,
	"Oliver Schoenborn" <oliver.schoenborn@utoronto.ca>
Cc: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>
Subject: Re: c++/9460: parse error on template member function
Date: Wed, 29 Jan 2003 10:09:39 +0100

 ----- Original Message -----
 From: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>
 To: "Oliver Schoenborn" <oliver.schoenborn@utoronto.ca>
 Cc: <gcc-gnats@gcc.gnu.org>
 Sent: Tuesday, January 28, 2003 10:14 PM
 Subject: Re: c++/9460: parse error on template member function
 
 > It would be different if you would call
 >   Foo().F1<A> ();
 > in which case you would have to use
 >   Foo().template F1<A> ();
 
 Sorry for the confusion. The problem is, the compiler still has symmetric
 behaviour:
 
 Foo().F1<A>() compiles with no errors, while it needs the template keyword.
 (accept-illegal)
 In my first code snippet, if you remove Bar::F1, the code fails to compile.
 (reject-legal).
 
 Giovanni Bajo
 


             reply	other threads:[~2003-01-29  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  9:16 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 15:46 Wolfgang Bangerth
2003-01-28 21:16 Wolfgang Bangerth
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=20030129091600.13674.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).