• 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: Precompiled headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Precompiled headers


  • Subject: Re: Precompiled headers
  • From: Quincey Morris <email@hidden>
  • Date: Fri, 28 Nov 2014 05:30:37 +0000

On Nov 27, 2014, at 20:45 , Fritz Anderson <email@hidden> wrote:

module imports are the way Apple thinks about frameworks, and #import-and-link-library will be a concession to compatibility.

You’ve read what’s on the box: Faster, smarter, more-stable precompilation

Thanks for the perspective. The way I read the clang docs, if the “modules” setting is on, then @import and #import are only lexicographically different. So I believe that particular issue is about appearance, not functionality.

FWIW, I started changing the framework imports from #import to @import. (The target template I used still had the old style, plus a framework item added to the project itself.) It makes me feel revolutionary, if nothing else.

 _______________________________________________
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: 
 >Precompiled headers (From: Quincey Morris <email@hidden>)
 >Re: Precompiled headers (From: Jens Alfke <email@hidden>)
 >Re: Precompiled headers (From: Quincey Morris <email@hidden>)
 >Re: Precompiled headers (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Precompiled headers
  • Next by Date: Xcode fonts blurry
  • Previous by thread: Re: Precompiled headers
  • Next by thread: Xcode fonts blurry
  • Index(es):
    • Date
    • Thread