On Tue, Jun 3, 2008 at 3:07 PM, Seth Willits <[EMAIL PROTECTED]> wrote: > I used to think that. Now I'm converting to making sure it truly is > returning an immutable object. There have been cases where I've changed it > under myself and run into problems. I figure if it says it's immutable, it'd > better be immutable.
I always do [[mutableInstance copy] autorelease] for two reasons: 1) I told you I've given you an immutable object. The other portions of my code had better be able to rely on that object's immutability. 2) It is not my responsibility to optimize creating immutable instances out of mutable instances. If it can be done, it is the mutable class's implementor's problem. (Of course that might be "me" the person, but it isn't "me" the client of the mutable class.) --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
