Re: Precompiled headers
Re: Precompiled headers
- Subject: Re: Precompiled headers
- From: Quincey Morris <email@hidden>
- Date: Thu, 27 Nov 2014 00:03:26 +0000
On Nov 26, 2014, at 15:49 , Jens Alfke <email@hidden> wrote:
One is a prefix header, which is what you describe above.
Ah, yes, I see now. Because of pre-compilation, I’ve looked at that build setting for years without making the distinction.
Follow-up questions for extra credit:
— Is there now an emerging trend to use @import in place of #import <> (for code that doesn’t need backward compatibility, of course)?
— Does the linker support automatic linking of frameworks mentioned in module @/#import statements? The clang web site describes this as not universally supported, but I don’t know if Apple’s ld does it, or for that matter whether Xcode provides the behavior even if ld doesn’t.
The first question only affects a savings of a few keystrokes AFAIK, but the second affects whether Cocoa frameworks still need to be manually added to Xcode projects.
|
_______________________________________________
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