public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Frey <daniel.frey@aixigo.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7065: unnamed derived classes/structs are rejected Date: Thu, 23 Jan 2003 09:06:00 -0000 [thread overview] Message-ID: <20030123090601.19082.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7065; it has been noted by GNATS. From: Daniel Frey <daniel.frey@aixigo.de> To: bangerth@dealii.org, daniel.frey@aixigo.de, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7065: unnamed derived classes/structs are rejected Date: Thu, 23 Jan 2003 09:58:13 +0100 bangerth@dealii.org wrote: > = > 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! Indeed. I noticed this problem when compiling code declaring a variable. I cut it down to report it to GNATS, but it seems I cut it down too much (as the problem with the old parser occured before it saw the variable). I consider it fixed now, the example I gave in the original error report is clearly illegal. Thanks to the whole GCC team. Regards, Daniel -- = Daniel Frey aixigo AG - financial training, research and technology Schlo=DF-Rahe-Stra=DFe 15, 52072 Aachen, Germany fon: +49 (0)241 936737-42, fax: +49 (0)241 936737-99 eMail: daniel.frey@aixigo.de, web: http://www.aixigo.de
next reply other threads:[~2003-01-23 9:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-23 9:06 Daniel Frey [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-23 3:01 bangerth 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=20030123090601.19082.qmail@sources.redhat.com \ --to=daniel.frey@aixigo.de \ --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: 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).