Re: Problem Archiving/Un-archiving Custom Objects

2016-01-24 Thread Dave
Thanks a lot for the clarification….. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-22 Thread Clark S. Cox III
> On Jan 22, 2016, at 06:14, Dave wrote: > > >> On 21 Jan 2016, at 23:40, Quincey Morris >> wrote: >> >> On Jan 21, 2016, at 15:22 , Dave > > wrote: >>> >>> I’m relying of the copy attribute for the NSString’s, do I need to change >>> these to do a [xxx

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-22 Thread Clark S. Cox III
> On Jan 22, 2016, at 06:14, Dave wrote: > > >> On 21 Jan 2016, at 23:40, Quincey Morris >> wrote: >> >> On Jan 21, 2016, at 15:22 , Dave > > wrote: >>> >>> I’m relying of the copy attribute for the NSString’s, do I need to change >>> these to do a [xxx

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-22 Thread Kyle Sluder
On Fri, Jan 22, 2016, at 08:14 AM, Dave wrote: > > > On 21 Jan 2016, at 23:40, Quincey Morris > > wrote: > > > > On Jan 21, 2016, at 15:22 , Dave > > wrote: > >> > >> I’m relying of the copy attribute for the NSString’s, do I need to change > >> these to do a

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-22 Thread Dave
> On 21 Jan 2016, at 23:40, Quincey Morris > wrote: > > On Jan 21, 2016, at 15:22 , Dave > wrote: >> >> I’m relying of the copy attribute for the NSString’s, do I need to change >> these to do a [xxx copy] too > > If you’re writing the setter yourself, yo

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-21 Thread Graham Cox
> On 22 Jan 2016, at 10:04 AM, Quincey Morris > wrote: > > In general, like in inits, you will want to assign directly to instance > variables rather than use property setters Same applies to -initWithCoder: If you call a lot of property setters there, performance is slow. It might not matt

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-21 Thread Quincey Morris
On Jan 21, 2016, at 15:22 , Dave wrote: > > I’m relying of the copy attribute for the NSString’s, do I need to change > these to do a [xxx copy] too If you’re writing the setter yourself, you must do the copy yourself. If you’re using the synthesized setter, it’s done for you. In your own

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-21 Thread Dave
> On 21 Jan 2016, at 23:04, Quincey Morris > wrote: > > On Jan 21, 2016, at 13:47 , Dave > wrote: >> >> myObjectCopy. pNodeIndexPath = self. pNodeIndexPath; //Copy >> Attribute on Property > > You have to be careful, depending on what’s alread

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-21 Thread Quincey Morris
On Jan 21, 2016, at 13:47 , Dave wrote: > > myObjectCopy. pNodeIndexPath = self. pNodeIndexPath; //Copy > Attribute on Property You have to be careful, depending on what’s already happened. If the object was copied with NSCopyObject, which might have happened in NSObjet’s copy

Re: Problem Archiving/Un-archiving Custom Objects

2016-01-21 Thread Jens Alfke
No, that’s weird, your code looks ok to me. Have you tried using the static analyzer? Or the address sanitizer? Or running with NSZombies? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comm