| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
From the converse point of view, if you want a mutable object because you know you'll change it, you mightn't want to limit your callers to providing a mutable version of the object... ultimately it's easier to call mutableCopy once in your target method than in some, most or even all your callers. As with the immutable case just mentioned, if the given object is already of the correct mutability you'll just end up retaining it.
| References: | |
| >Copy and release (From: Nicko van Someren <email@hidden>) | |
| >Re: Copy and release (From: Evan Schoenberg <email@hidden>) | |
| >Re: Copy and release (From: Nicko van Someren <email@hidden>) | |
| >Re: Copy and release (From: Paul Sargent <email@hidden>) | |
| >Re: Copy and release (From: Wade Tregaskis <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.