• 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: Mutability
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mutability


  • Subject: Re: Mutability
  • From: Angela Brett <email@hidden>
  • Date: Wed, 21 Nov 2001 17:43:42 +1300

Why do you care??

If you need a mutable version of a collection make a mutableCopy of it.

That's true, but consider the case where the object is deep in nested NSArrays or NSDictionaries. Assuming the object is immutable means you have to add the mutableCopy of it to its parent array/dictionary in place of the original object, and if you don't know whether the parent is mutable or not you'll also have to make a mutableCopy of that and add it to its parent, and so on until you get to the 'root' object. That's quite a lot of unnecessary steps if the original objects were actually mutable anyway and you didn't know it. Or perhaps this post is all newbie nonsense. :)
--
Angela Brett email@hidden http://acronyms.co.nz/angela
A mathematician is a machine for turning coffee into theorems -- Paul Erdos


  • Follow-Ups:
    • Re: Mutability
      • From: Raphael Sebbe <email@hidden>
    • Re: Mutability
      • From: Julien Dufour <email@hidden>
References: 
 >Re: Mutability (From: Vince DeMarco <email@hidden>)

  • Prev by Date: Re: Rects and points...
  • Next by Date: Re: Rects and points...
  • Previous by thread: Re: Mutability
  • Next by thread: Re: Mutability
  • Index(es):
    • Date
    • Thread