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: Jeffrey Schmidt <email@hidden>
- Date: Tue, 22 Sep 2009 14:57:47 -0500
It looks like this has to do with some ambiguities in what a typedef of void is trying to do in this context. In C it's ok to do this, but it isn't in C++. Is that typedef just acting to rename void, and then the function should take no parameters? Or is it specifying the type of a parameter? C++ decided to say it's just not allowed. At least that's my understanding of this error.
--
Jeffrey Schmidt, senior software architect
MultiAd® Creator and Creator Server
email@hidden
_______________________________________________
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