public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "caolanm at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/20589] error: '<anonymous enum>' is/uses anonymous type'
Date: Wed, 23 Mar 2005 11:54:00 -0000	[thread overview]
Message-ID: <20050323115343.18806.qmail@sourceware.org> (raw)
In-Reply-To: <20050322154540.20589.caolanm@redhat.com>


------- Additional Comments From caolanm at redhat dot com  2005-03-23 11:53 -------
The workaround is trivial. But I'm still confused as to what exactly causes gcc
to treat unnamed enums so much differently that named ones. It would be great if
I could get some clarity on this. I have a handful of cases like this in the
openoffice.org code base and OOo is reluctant to take the patches to fix unless
sure it's currently invalid.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20589


  parent reply	other threads:[~2005-03-23 11:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 15:45 [Bug c++/20589] New: " caolanm at redhat dot com
2005-03-22 15:46 ` [Bug c++/20589] " caolanm at redhat dot com
2005-03-22 16:10 ` pinskia at gcc dot gnu dot org
2005-03-22 16:16 ` mmitchel at gcc dot gnu dot org
2005-03-23 11:54 ` caolanm at redhat dot com [this message]
2005-03-23 16:57 ` pinskia at gcc dot gnu dot org
2005-03-23 18:53 ` bangerth at dealii dot org
2005-03-23 19:12 ` caolanm at redhat dot com
2005-03-23 19:24 ` bangerth at dealii dot org
2005-03-23 19:28 ` mark at codesourcery dot com
2005-03-23 21:56 ` bangerth at dealii dot org
2005-03-26  4:20 ` gdr at integrable-solutions dot net
2005-03-26 22:53 ` bangerth at dealii dot org
2005-03-27  3:18   ` Gabriel Dos Reis
2005-03-27  3:18 ` gdr at integrable-solutions dot net
2005-08-05  3:43 ` sethml at google dot com
2005-08-05  3:48 ` pinskia at gcc dot gnu dot org
2005-08-05  3:48 ` pinskia at gcc dot gnu dot org
2005-08-05  3:49 ` mark at codesourcery dot com

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=20050323115343.18806.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).