public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	picaud.vincent@wanadoo.fr
Subject: Re: c++/9380: nested template problem for methods without argument : parsing error
Date: Tue, 21 Jan 2003 14:15:00 -0000	[thread overview]
Message-ID: <20030121141505.28979.qmail@sources.redhat.com> (raw)

Synopsis: nested template problem for methods without argument : parsing error

State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Tue Jan 21 14:15:05 2003
State-Changed-Why:
    Not a bug.  Your code inside 'foo_2':
      a.how_many<Vertex>();
    'a' depends on the template parameter 'dim' so the compiler
    doesn't know if 'how_many' is a variable, a type, or a
    template.  For example, you can declare a specialization
      template<> class A<Volumn> { int how_many; }
    Then 'A<Vertex>.how_many' is a template function but
    'A<Volumn>.how_many' is a variable.  
    
    When you are referring to a template when the context is 
    template parameter dependent, you need the 'template' 
    keyword as in:
      a.template how_many<Vertex>();
    The same applies to the example in the Fix section:
      a.template how_many<Vertex>(id_foo<Vertex>());

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9380


             reply	other threads:[~2003-01-21 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 14:15 lerdsuwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-22 10:56 Vincent PICAUD
2003-01-20 23:26 picaud.vincent

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=20030121141505.28979.qmail@sources.redhat.com \
    --to=lerdsuwa@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=picaud.vincent@wanadoo.fr \
    /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).