public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, martin@loewis.home.cs.tu-berlin.de, nathan@gcc.gnu.org, sebor@roguewave.com Subject: Re: c++/189: parse error in qualified member name lookup Date: Wed, 13 Feb 2002 02:21:00 -0000 [thread overview] Message-ID: <20020213102152.6364.qmail@sources.redhat.com> (raw) Synopsis: parse error in qualified member name lookup State-Changed-From-To: feedback->analyzed State-Changed-By: nathan State-Changed-When: Wed Feb 13 02:21:52 2002 State-Changed-Why: I've got a reponse from John Spicer (The edg front end accepts this code). The standard as written is unclear about class name injection, and DR 176 documents the problem. As that is an accepted DR, we should implement it (sometime...) http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=189
next reply other threads:[~2002-02-13 10:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-13 2:21 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-20 18:45 Wolfgang Bangerth 2001-12-24 13:22 nathan 2001-12-21 14:30 nathan
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=20020213102152.6364.qmail@sources.redhat.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=martin@loewis.home.cs.tu-berlin.de \ --cc=sebor@roguewave.com \ /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: linkBe 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).