#define/enum conflict

Article View: gnu.gcc.help

Article #49473

#49473

From: Steve Harris
Date: Mon, 24 Jan 1994 19:26

10 lines
914 bytes

gcc version 2.5.4

If a #define symbol conflicts with an enum symbol
gcc reports no error unless the #define comes BEFORE
the enum.
When the #define comes after the enum the #define value
seems to take precedence and no compiler warning/error
is given.

Is this a bug or standard c?

Technical Details

Message-ID: <9401241924.AA18389@rdxsun38.aud.alcatel.com>

Path:

arc1-ca.pugleaf.net!gmd.de!xlink.net!zib-berlin.de!netmbx.de!Germany.EU.net!EU.net!howland.reston.ans.net!cs.utexas.edu!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,e6aabe672a9e8f53,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1994-01-24 17:33:52 PST
Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!zib-berlin.de!netmbx.de!Germany.EU.net!EU.net!howland.reston.ans.net!cs.utexas.edu!not-for-mail
From: slharris@rdxsun38.aud.alcatel.com (Steve Harris)
Newsgroups: gnu.gcc.help
Subject: #define/enum conflict
Date: 24 Jan 1994 13:26:37 -0600
Organization: UTexas Mail-to-News Gateway
Lines: 10
Sender: daemon@cs.utexas.edu
Message-ID: <9401241924.AA18389@rdxsun38.aud.alcatel.com>
NNTP-Posting-Host: cs.utexas.edu