Dear all,
I guess I'll add my 2 cents.
I don't think .mm should be used unless the class structure is
objective-c++. To me this means that the classes are declared in .h
files with the
@interface foo
{
}
@end
construct and the implementation in the .mm files with
@implementation foo
@end
with all of the associated objective-c++ syntax. To me, this is what
is meant when someone says the file "contains" objective-c++. By way
of analogy, a c++ file may sometimes contain inline assembly code,
but we don't label that file as .a because it "contains" assembly
code. So I think a lot more needs to be done than just renaming the
files.
If we follow the objective-c++ constructs within the .mm files, it is
fine with me to go ahead and change.
Regards,
Mike
