Re: CGFloat and NS_BUILD_32_LIKE_64
Re: CGFloat and NS_BUILD_32_LIKE_64
- Subject: Re: CGFloat and NS_BUILD_32_LIKE_64
- From: Rick Mann <email@hidden>
- Date: Fri, 27 Feb 2015 16:35:39 -0800
Because once upon a time I ran into an issue around the size of CGFloat and someone told me to use NS_BUILD_32_LIKE_64, and that took care of it. Ever since then, I believed NS_BUILD_32_LIKE_64 controlled the size of CGFloat.
> On Feb 27, 2015, at 16:32 , Roland King <email@hidden> wrote:
>
>
>> On 28 Feb 2015, at 08:14, Rick Mann <email@hidden> wrote:
>>
>> I thought setting NS_BUILD_32_LIKE_64 = 1 would make CGFloat be double, but CGFloat seems to be conditionalized on __LP64__ (at least, on iOS.
>
> Why did you think that? The docs say
>
> The NS_BUILD_32_LIKE_64 preprocessor macro works in a different manner. It declares NSInteger to be long (instead of int) and NSUInteger to be long unsigned int even on 32-bit portions of the source base.
>
> and that’s all they say. Nothing about CGFloat
>
>>
>> I'm building iOS for both 32 and 64 bit devices. What should I do here? I'm trying to get rid of a bunch of implicit conversion warnings. Thanks.
>
> use explicit casts.
>
--
Rick Mann
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden