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,
	rmgiroux@hotmail.com
Subject: Re: c++/925: [parser]Follow-up to c++/909 with more info
Date: Tue, 31 Dec 2002 00:41:00 -0000	[thread overview]
Message-ID: <20021231084122.30547.qmail@sources.redhat.com> (raw)

Synopsis: [parser]Follow-up to c++/909 with more info

State-Changed-From-To: suspended->closed
State-Changed-By: lerdsuwa
State-Changed-When: Tue Dec 31 00:41:21 2002
State-Changed-Why:
    Fixed in 3.4 after parser merge.  Not that GCC produces the following error message which is correct.
    
    testExp.cpp:35: request for member `f' in `e', which is of non-aggregate type `A ()(A::Nested)'

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


             reply	other threads:[~2002-12-31  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  0:41 lerdsuwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-16 23:36 nathan
2001-11-16 23:36 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=20021231084122.30547.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=rmgiroux@hotmail.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: 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).