On Fri, 31 Jul 2015 12:15:10 +0200, Jean-Daniel Dupas said:
>
>> Le 30 juil. 2015 à 18:26, Fritz Anderson a écrit :
>>
>> On 30 Jul 2015, at 11:03 AM, Trygve Inda wrote:
>>
>>> It seems Apple is using retain rather than copy for NSString properties in
>>> an NSManagedObject subclass.
>>>
>>>
> Le 30 juil. 2015 à 18:26, Fritz Anderson a écrit :
>
> On 30 Jul 2015, at 11:03 AM, Trygve Inda wrote:
>
>> It seems Apple is using retain rather than copy for NSString properties in
>> an NSManagedObject subclass.
>>
>> I was always under the impression that copy should be used for NSStrin
> On Jul 30, 2015, at 9:03 AM, Trygve Inda wrote:
>
> It seems Apple is using retain rather than copy for NSString properties in
> an NSManagedObject subclass.
So, you’re saying that if you store an NSMutableString into a dynamic
NSManagedObject property, and then mutate the original string, t
On 30 Jul 2015, at 11:03 AM, Trygve Inda wrote:
> It seems Apple is using retain rather than copy for NSString properties in
> an NSManagedObject subclass.
>
> I was always under the impression that copy should be used for NSString, so
> why the retain??
For an immutable string, -copy is implem
It seems Apple is using retain rather than copy for NSString properties in
an NSManagedObject subclass.
I was always under the impression that copy should be used for NSString, so
why the retain??
Trygve
___
Cocoa-dev mailing list (Cocoa-dev@lists.a
