public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Farfetch'd" <farfetchd@libero.it>
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 02:36:00 -0000	[thread overview]
Message-ID: <20030128023600.4619.qmail@sources.redhat.com> (raw)

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

From: "Farfetch'd" <farfetchd@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<oliver.schoenborn@utoronto.ca>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc:  
Subject: Re: c++/9460: parse error on template member function
Date: Tue, 28 Jan 2003 03:34:27 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=9460
 
 I am not absolutely sure there is no bug here. For example, look at the
 following snippet:
 
 ------------
 struct Foo
 {
     template <typename T>
     void F1(void) {}
 };
 
 template <typename A>
 struct Bar
 {
    void F2(void)
    {
        Foo f;
        f.F1<int>();
    }
 
     template <typename T>
     void F1(void) {}
 };
 
 template Bar<int>;
 ------------
 
 The previous snippet is accepted by G++ but it shouldn't since it's not
 legal. The compiler is fooled by Bar::F1<> having the same name of
 Foo::F1<>. Also the following code is accepted as well and should not:
 
 ------------
 struct Foo
 {
     template <typename T>
     void F1(void) {}
 };
 
 template <typename A>
 struct Bar
 {
    void F2(void)
    {
       Foo().F1<int>();
    }
 };
 
 template Bar<int>;
 ------------
 
 since it's still missing the template keyword in the member template call.
 So it's not a case of reject-legal, but of accept-illegal.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-01-28  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28  2:36 Farfetch'd [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 21:16 Wolfgang Bangerth
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=20030128023600.4619.qmail@sources.redhat.com \
    --to=farfetchd@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).