At 10:46 +0200 5/9/05, Frank Heckenbach wrote:
Thorsten Glaser wrote:
Peter N Lewis dixit:
gp works fine with including objective C files via:
{$L file.m}
but does not include the language extension for .m.
Isn't .mm Objective-C++ and should be added too?
Maybe I'm naive, but if anyone could explain to me how the letters "mm" stand for "Objective-C++", this might really be an enlightenment. Perhaps I should just add any 1/2 letter combination as some kind of C variant. ;-)
I believe .m dates back to the NeXT GNUNextStep days of Objective-C. I have no idea what the m is suppose to stand for if anything.
Seriously, if there are really the "official" file name suffixes (I don't know Objective-C[++] myself, so I have no idea), I'll add them.
Yes, they are official, see:
Preprocessing Mixed-Language Code http://developer.apple.com/documentation/Cocoa/Conceptual/CarbonCocoaDoc/Articles/CompilerPreprocessors.html#//apple_ref/doc/uid/20002400-DontLinkElementID_445753a
Table 1 : Filename extensions and compilation Filename extension Indicates to the compiler .c C source code that must be preprocessed .m Objective-C source code .mm Objective-C++ source code .h C header file (not to be compiled or linked) .cc, .cp, .cxx, .cpp, .c++, .C C++ source code that must be preprocessed
Objective-C and C++ are primarily used under Mac OS X, but are also used under GNUstep and can be used on any platform as far as I know.
Enjoy, Peter.