• 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
Re: NSMutable setArray Behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSMutable setArray Behavior


  • Subject: Re: NSMutable setArray Behavior
  • From: Kyle Sluder <email@hidden>
  • Date: Tue, 20 Apr 2010 14:48:31 -0700

On Tue, Apr 20, 2010 at 2:07 PM, Jens Alfke <email@hidden> wrote:
> In general I can't think of any deep-copy behavior in any of the Cocoa
> collection classes. With one exception*, objects only get copied when you
> explicitly call -copy. And even -copy is implemented shallowly in existing
> classes (so copying an NSArray results in a new array that contains the same
> objects, not copies of those objects.)

On Tiger and earlier, custom subclasses of the collection classes
would deep-copy. See the Leopard release notes:
http://developer.apple.com/iphone/library/releasenotes/Cocoa/Foundation.html

--Kyle Sluder
_______________________________________________

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

References: 
 >NSMutable setArray Behavior (From: Brent Fulgham <email@hidden>)
 >Re: NSMutable setArray Behavior (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: NSMutable setArray Behavior
  • Next by Date: Re: Carbon pasteboard/service events not firing in Cocoa app
  • Previous by thread: Re: NSMutable setArray Behavior
  • Next by thread: Why is compiler warning for +setKeys:triggerChangeNotificationsForDependentKey: ??
  • Index(es):
    • Date
    • Thread