public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: daniel.frey@aixigo.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org
Subject: Re: c++/7065: unnamed derived classes/structs are rejected
Date: Thu, 23 Jan 2003 03:01:00 -0000 [thread overview]
Message-ID: <20030123030132.32176.qmail@sources.redhat.com> (raw)
Synopsis: unnamed derived classes/structs are rejected
State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Thu Jan 23 03:01:31 2003
State-Changed-Why:
Fixed with new parser. The only valid use of an unnamed struct
is to either declare a typedef, or to name a variable:
------------------------
class A {};
typedef class : A {} B;
class : A {} a;
------------------
Both uses compile just fine now. That being said, what
an abomination of the language!
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7065
next reply other threads:[~2003-01-23 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 3:01 bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-23 9:06 Daniel Frey
2002-07-03 12:46 nathan
2002-06-18 6:16 daniel.frey
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=20030123030132.32176.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=daniel.frey@aixigo.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--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).