Re: xcode & c++
Re: xcode & c++
- Subject: Re: xcode & c++
- From: koko <email@hidden>
- Date: Fri, 02 Mar 2012 18:20:50 -0700
| I disagree. If you are doing development for Win and Mac with as much a common code base as possible the compiler setting is the only way to go.
-koko
On Mar 2, 2012, at 5:51 PM, Fritz Anderson wrote: On 2 Mar 2012, at 3:03 PM, koko wrote: This way each file keeps its 'native' extension … .cpp or .m and the project builds nicely.
This a file that relies on including a C++ header. The .m extension is a bug, and should not be preserved. Jiggering the compiler settings (which will be invisible to anyone who sees the file) is fragile, misleading, and preserves the bug for every subsequent user.
— F
|
_______________________________________________
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