This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11853] long enum constant name results in an error
- From: "agri at desnol dot ru" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Aug 2003 15:05:21 -0000
- Subject: [Bug c/11853] long enum constant name results in an error
- References: <20030808104734.11853.agri@desnol.ru>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11853
agri at desnol dot ru changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From agri at desnol dot ru 2003-08-08 15:05 -------
:-) i never though that even developers doesn't know what do gcc do
now... let me try again
let me cat part of netinet/in.h
enum {
IPPROTO_IP = 0,
#define IPPROTO_IP IPPROTO_IP
oopps it's already has such a define.... it doesn't complain about it
it complains on the line (one line before define)
IPPROTO_HOPOPTS = 0
not on the line
#define IPPROTO_HOPOPTS IPPROTO_HOPOPTS
and if i edit that line as
IPPROTO_HOPO = 0,
#define IPPROTO_HOPO IPPROTO_HOPO
it won't complain about at all