Re: gcc 4.2 generates error that was OK before
Re: gcc 4.2 generates error that was OK before
- Subject: Re: gcc 4.2 generates error that was OK before
- From: "E. Wing" <email@hidden>
- Date: Tue, 22 Sep 2009 17:52:20 -0700
On 9/22/09, Steve Mills <email@hidden> wrote:
> On Sep 22, 2009, at 15:41:46, Jens Alfke wrote:
>
>> That's not a parameter of type 'void'. That 'void' keyword is just a
>> marker indicating that the function takes no parameters. This is
>> syntactic cruft introduced in ANSI C to work around the ambiguity of
>> pre-ANSI prototype-less function declaration syntax.
>
> And that's what I meant by "single void parm".
>
>> I would guess there used to be a glitch in GCC where it expanded
>> typedefs before looking for the 'void' marker, so it allowed the
>> syntax in question; and now in 4.2 it doesn't do that anymore, and
>> detects that the declaration is bogus.
>
> Maybe. I'm just hoping for an answer from someone who knows the actual
> answer.
>
I blogged on this last week. I encountered the same problem in OpenAL.
http://playcontrol.net/ewing/jibberjabber/another_c_vs_c_incompatibil.html
-Eric
_______________________________________________
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