• 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: Jens Alfke <email@hidden>
  • Date: Sat, 03 Mar 2012 13:25:42 -0800


On Mar 2, 2012, at 5:20 PM, koko wrote:

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.

It’s not the way Chromium does it, and IIRC it’s not the way Safari does it. Both of those are very large cross-platform projects that intermix C++ and Objective-C. They use “.mm” suffixes for any Obj-C files that use C++.

Fundamentally, if you have a source file that is Objective-C and needs to use C++ features, then the language dialect you are using is Objective-C++, and the file’s extension should be “.mm” to reflect that.

—Jens
 _______________________________________________
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>)
 >Re: xcode & c++ (From: Fritz Anderson <email@hidden>)
 >Re: xcode & c++ (From: koko <email@hidden>)

  • Prev by Date: Re: Subversion access suddenly flaky?
  • Next by Date: Re: Xcode - AN APPLE OPPORTUNITY!
  • Previous by thread: Re: xcode & c++
  • Next by thread: Re: xcode & c++
  • Index(es):
    • Date
    • Thread