public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/4232: template instantiation in function body using a template argument fails
Date: Sun, 09 Sep 2001 13:46:00 -0000 [thread overview]
Message-ID: <20010909204602.16519.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/4232; it has been noted by GNATS.
From: Alexandre Oliva <aoliva@redhat.com>
To: Philip Martin <philip_martin@ntlworld.com>
Cc: gcc-gnats@gcc.gnu.org, vyzo@media.mit.edu, gcc-bugs@gcc.gnu.org
Subject: Re: c++/4232: template instantiation in function body using a template argument fails
Date: 09 Sep 2001 17:41:23 -0300
On Sep 9, 2001, Philip Martin <philip_martin@ntlworld.com> wrote:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4232&database=gcc
> This is not a gcc bug, your code is invalid.
Not really. The `template' keyword should only be required below in
case the type of `f' was dependent on template arguments. But this is
not the case, so `template' is optional. Using it is just a
work-around for GCC.
> template <typename _type>
> _type moo( const foo& f ) { return f.template cast_foo<_type>(); }
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next reply other threads:[~2001-09-09 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 13:46 Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 6:48 lerdsuwa
2001-09-09 12:56 Philip Martin
2001-09-04 17:06 vyzo
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=20010909204602.16519.qmail@sourceware.cygnus.com \
--to=aoliva@redhat.com \
--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).