Igor Delovski Board

[Jean Jacques]

.c vs .C in Xcode project compilation

"I noticed that the other 3 corresponding code files (all also trivial
object definitions I was using as a test) were called [filename].C
while the code file associated with the non-compiling header file was
called [filename].c - that is, the ones with UPPERCASE C as the
extension would compile while the LOWERCASE .c extension would not
compile.

Changning the .c to a .C allowed this trivial class to compile in XCode
and the header file no longer reported any error."

[delovski]

Another surprise: Help needed switching from CW 9 to XCode

"I've been trying to prep a Codewarrior 9 project for conversion to
XCode and I've run into all manner of nasty compile errors. Stuff that
doesn't make any sense."

[delovski]

c++ interface book

"In your programs, name your ".m" files with a ".mm" extension. The
compiler recognizes .mm as containing both Objective-C and C++. Objective-C
objects can hold pointers to C++ objects."

[delovski]

CarbonDev: Compiler Detection

"You can always detect GCC itself with the __GNUC__ macro, and Apple's
GCC with the __APPLE__ macro. The simplest way to detect more specific
diferences is to use the macros provided by TargetConditionals.h."