On Feb 15, 2012, at 00:50 , Uli Kusterer wrote: > Why would there ever be an object that is not -isEqual: to itself? Now you've > lost me.
Sorry, it was a poor choice of words. I was just acknowledging the difference between (say) a NSMutableDictionary whose internal state changes over time without affecting the objects it's isEqual to (just itself, in this case) and NSMutableString, whose internal state changes over time and does affect what it's isEqual to. There are, of course, potentially, objects that aren't isEqual to themselves. An object representing the current (running) time might be designed to fail [timeNow isEqual: timeNow]. But I can't think of an example that isn't pathological, and such objects weren't what I had in mind earlier. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
