public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gianni@mariani.ws,
	nobody@gcc.gnu.org
Subject: Re: c++/10514: incorrect parsing of template instatiation with pointer-to-member variables
Date: Mon, 28 Apr 2003 13:56:00 -0000	[thread overview]
Message-ID: <20030428135614.13165.qmail@sources.redhat.com> (raw)

Synopsis: incorrect parsing of template instatiation with pointer-to-member variables

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Mon Apr 28 13:56:14 2003
State-Changed-Why:
    Confirmed.
    The parser hickups affect all release versions since 2.95.x,
    as well as 3.3 branch and mainline.
    
    BTW, not only using
      i_1->A::TFUNC_A<w_a,w_b>( m_b1 );
    but also writing
      i_1->template TFUNC_A<w_a,w_b>( m_b1 );
    makes the code compile.
    
    The problem can also be demonstrated with the following code snippet:
    
    ============================snip here===============================
    struct A
    {
        template <int> void foo() {}
    };
    
    struct B
    {
        template <int> void bar (A* p)
        {
            p->foo<0>(); // compiler trouble
        }
    
        void baz (A* p)
        {
            bar<0>(p);
        }
    };
    ============================snip here===============================
    
    Regards,
    Volker

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


             reply	other threads:[~2003-04-28 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28 13:56 reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16  1:22 giovannibajo
2003-04-27 15:36 gianni

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=20030428135614.13165.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gianni@mariani.ws \
    --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).