Re: Problem Archiving/Un-archiving Custom Objects
Re: Problem Archiving/Un-archiving Custom Objects
- Subject: Re: Problem Archiving/Un-archiving Custom Objects
- From: Quincey Morris <email@hidden>
- Date: Thu, 21 Jan 2016 15:40:16 -0800
- Feedback-id: 167118m:167118agrif8a:167118sLTZHyw3Wm:SMTPCORP
On Jan 21, 2016, at 15:22 , Dave <email@hidden> wrote:
>
> I’m relying of the copy attribute for the NSString’s, do I need to change these to do a [xxxxxxx 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 code, you may as well be liberal with ‘copy’. It’s basically free (in run-time cost) in situations where you don’t need it. You don’t save anything by leaving it out.
_______________________________________________
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