Possible XCode C compiler bug
Possible XCode C compiler bug
- Subject: Possible XCode C compiler bug
- From: Ken Tozier <email@hidden>
- Date: Sun, 22 Feb 2004 22:43:26 -0500
I was getting an "incompatible types" error when compiling a source
file and it turned out to be a missing semicolon (my fault). What's odd
though, is that the compiler seemed to have no problem squirreling away
this one unterminated declaration, going on to successfully process
subsequent declarations and then resume looking for a terminating
semicolon when it encountered another numeric type. for example:
// missing semicolon
OSErr theErr = noErr
// these compiled fine
FSSpec mapFolder = {0},
mapFileSpec = {0};
Handle aliasHandle = NULL;
// something fishy happens here
long bufferSize = 120,
writeSize,
recCount;
// attempting the following assignment
writeSize = bufferSize;
Yeilds -> error: conflicting types for "writeSize"
Putting the semicolon solves the problem, but this skipping over other
declares and failing in the "long" declaration, is really strange
behavior in my opinion.
Does anyone else think this is a bug?
Ken
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.