Re: Making GCC less sensitive about duplicate typedefs?
Re: Making GCC less sensitive about duplicate typedefs?
- Subject: Re: Making GCC less sensitive about duplicate typedefs?
- From: Steve Checkoway <email@hidden>
- Date: Mon, 19 Jun 2006 22:54:40 -0700
On Jun 19, 2006, at 6:57 PM, Justin C. Walker wrote:
On Jun 19, 2006, at 16:17 , Mark Wagner wrote:
The following C code compiles just fine in CodeWarrior, but gcc gives
an error of "error: conflicting types for 'dummy'". How do I get
this
sort of thing to compile with gcc?
What version of the compiler are you using? On 10.4.6, with Xcode
2.3 installed, both gcc 3.3 and gcc 4.0 do not give this error. It
complains that you are redefining a variable, which I think is the
right response.
It doesn't say you're redefining a variable and I'd be shocked if it
did. It claims that you're redefining the typedef:
$ gcc -x c -Wall - <<EOF
> typedef char dummy;
> typedef char dummy;
> int main() { return 0; }
> EOF
<stdin>:2: error: redefinition of typedef ‘dummy’
<stdin>:1: error: previous declaration of ‘dummy’ was here
gcc-3.3 gives:
<stdin>:2: error: redefinition of `dummy'
<stdin>:1: error: `dummy' previously declared here
I believe this is in line with the standard.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden