• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: xcode & c++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xcode & c++


  • Subject: Re: xcode & c++
  • From: Scott Ribe <email@hidden>
  • Date: Fri, 02 Mar 2012 21:56:47 -0700

On Mar 2, 2012, at 2:03 PM, koko wrote:

> This way each file keeps its 'native' extension …  .cpp or .m and the project builds nicely.

Bad idea. If a file contains C++, it can hardly be considered correct to refer to .m as its "native" extension. If you go mixing Objective-C and C++ willy-nilly without understanding what is used where, you will run into problems, regardless of compiler settings.

--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice





 _______________________________________________
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


References: 
 >xcode & c++ (From: Livio Isaia <email@hidden>)
 >Re: xcode & c++ (From: Luca Ciciriello <email@hidden>)
 >Re: xcode & c++ (From: koko <email@hidden>)

  • Prev by Date: Re: Xcode 4 Preference for Children Paths
  • Next by Date: Re: Xcode - An Apple Embarrassment
  • Previous by thread: Re: xcode & c++
  • Next by thread: Re: xcode & c++
  • Index(es):
    • Date
    • Thread