public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: gcc@gcc.gnu.org
Subject: Re: C++ parser issue [templ.res]
Date: Tue, 28 Jan 2003 13:29:00 -0000	[thread overview]
Message-ID: <m3hebtvfqu.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200301281703.00210.janvandijkinjapan@yahoo.co.jp>

Jan Van Dijk <janvandijkinjapan@yahoo.co.jp> writes:

[...]

| Qualifying i as B<T>::i (thus making i a dependent name explicitly)
| fixes the problem, see ugly(). To my surprise, look up of member
| variables is now different from that of member functions: f() does
| not need to be qualified (see good()). Either I missed a crucial 
| section of the standard (which one?), or this is a parser bug.
| 
Parser bug.

-- Gaby

  reply	other threads:[~2003-01-28  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 12:48 Jan Van Dijk
2003-01-28 13:29 ` Gabriel Dos Reis [this message]
2003-01-28 13:54 ` Nathan Sidwell
2003-01-28 19:21 ` Mark Mitchell
2003-01-28 20:02   ` Gabriel Dos Reis
2003-01-29 15:28     ` Jan Van Dijk
2003-01-29 15:37 Richard Guenther

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=m3hebtvfqu.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@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).