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: Steve Mills <email@hidden>
- Date: Tue, 22 Sep 2009 14:38:59 -0500
On Sep 22, 2009, at 14:32:01, Alastair Houghton wrote:
Are you compiling this in (ObjC-)C++, perchance?
Yes, C++ - it's a .cpp file.
I ask because the C++ language syntax has all kinds of problems
thanks to the thoughtless way its grammar was extended (no, I do not
worship Stroustrup, unlike---apparently---half the developer
community). It may be that the compiler is for some reason treating
your function declaration as a declaration of a variable with an
initialiser and then barfing.
If that *is* the cause of the problem, I wouldn't be entirely
surprised to discover that the standard mandates it. It often seems
to come up with---on the face of things unreasonable---meanings for
things, but if you read it carefully you can usually see why it was
decided that way.
I'm not sure what you're saying the problem might be.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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