• 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: NSMutableArray morphs itself into an NSArray?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: NSMutableArray morphs itself into an NSArray?


  • Subject: RE: NSMutableArray morphs itself into an NSArray?
  • From: "Jonathan E. Jackel" <email@hidden>
  • Date: Mon, 8 Mar 2004 14:07:10 -0500

> If you use +array then the mutable array will be put in the
> auto-release pool. It won't get auto-released -- because you retain it
> -- but there is no need for it to go in the auto-release pool at all.

I think you meant to say the array won't get "dealloced." The array most
certainly will get autoreleased, and its retain count will be reduced. But
if another object has retained it, it won't be dealloced because its retain
count will be > 0.

Jonathan
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Re: NSMutableArray morphs itself into an NSArray? (From: Dustin Voss <email@hidden>)

  • Prev by Date: Calling tableView:setObjectValue directly...
  • Next by Date: Re: NSMutableArray morphs itself into an NSArray?
  • Previous by thread: Re: NSMutableArray morphs itself into an NSArray?
  • Next by thread: Re: NSMutableArray morphs itself into an NSArray?
  • Index(es):
    • Date
    • Thread