Re: KVC, binding multiple properties, top level object
Re: KVC, binding multiple properties, top level object
- Subject: Re: KVC, binding multiple properties, top level object
- From: Trygve Inda <email@hidden>
- Date: Sun, 13 Jul 2014 18:55:21 -0700
- Thread-topic: KVC, binding multiple properties, top level object
>
> On 14 Jul 2014, at 7:29 am, Trygve Inda <email@hidden> wrote:
>
>> Is NSInteger treated the same way? This page does not mention it:
>
> NSInteger is a typedef for 'long', which size depends on the platform (32/64
> bit), so valueForKey: will wrap it as a NSNumber using type 'long'. That's
> safe across archives that are used in both 32 and 64 bit ISAs, though with
> loss of precision if a 64-bit archive was dearchived on 32-bit (and this might
> become a permanent loss if the data is reachived and then opened in 64-bit).
> Scalar properties that explicitly declare 'long long' would be always 64-bit.
> I doubt if this is an issue in practice.
So what is the purpose of the NSInteger access within NSNumber eg
integerValue and setIntegerValue ?
Please disregard my last message - it got sent before I could stop it. :-)
_______________________________________________
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