• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Why use copy in value setters?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why use copy in value setters?


  • Subject: Why use copy in value setters?
  • From: Larry Gerndt <email@hidden>
  • Date: Mon, 22 Aug 2005 08:51:41 -0700

Apple recommends that setters which provide "values" as opposed to "entities" should copy the value object instead of retain it. Quoting Apple:

"The general rule is this: When the object assigned to an instance variable is a value object—that is, an object that represents some attribute such as a string, date, number, or corporate record—you should copy it. Otherwise, it’s an entity object such as an NSView or an NSWindow and you should retain it."

My question is simply why?
--
Larry Gerndt
Blog: CoreData
AIM: SonOfTheSonOfMan
"Let the truth be told though the heavens fall" -- James Garrison



_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Why use copy in value setters?
      • From: Jim Correia <email@hidden>
    • Re: Why use copy in value setters?
      • From: Jim Hamilton <email@hidden>
  • Prev by Date: Clearing NSTableView on unbind
  • Next by Date: Re: Clearing NSTableView on unbind
  • Previous by thread: Re: Clearing NSTableView on unbind
  • Next by thread: Re: Why use copy in value setters?
  • Index(es):
    • Date
    • Thread