| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
What I thought I was saying was that, if you need a mutable copy because you need to change it, you'd make one (probably by calling mulatbleCopy). If you didn't you store a reference (probably returned from retain). It doesn't matter if the class your working on is mutable or not.
If everything was mutable, you should be incurring extra costs because of unnecessary copies. Your code should only copy when it's necessary.
| 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>) | |
| >Re: Copy and release (From: Paul Sargent <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.