Re: Clang __has_feature check for new 'nullable' language extensions?
Re: Clang __has_feature check for new 'nullable' language extensions?
- Subject: Re: Clang __has_feature check for new 'nullable' language extensions?
- From: Roland King <email@hidden>
- Date: Thu, 12 Feb 2015 15:55:04 +0800
> On 12 Feb 2015, at 15:19, Jens Alfke <email@hidden> wrote:
>
> I’m starting to add the new Objective-C nullability indicators (nullable, nonnull, #pragma clang assume_nonnull, etc.) to my framework's headers. But how can I do so in a backward-compatible way, so that clients building with earlier versions of Xcode can use the headers without errors?
>
> I’m guessing there’s a Clang __has_feature(…) parameter that can be used to test for this, but it’s not mentioned in the release notes. Anyone know what it might be?
>
> —Jens
> _______________________________________________
I’m guessing it’s
__has_feature( nullability )
from diffing strings in the two versions of clang.
_______________________________________________
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