Re: copy & isEqual nightmares
Re: copy & isEqual nightmares
- Subject: Re: copy & isEqual nightmares
- From: Mike Abdullah <email@hidden>
- Date: Fri, 17 Feb 2012 23:37:58 +0000
On 17 Feb 2012, at 20:33, Ben Kennedy wrote:
> On 16 Feb 2012, at 3:54 pm, Ken Thomases wrote:
>
>> In other words, you're being silly. It's clear to everyone that -[NSString isEqual:] must have semantics built on -[NSString isEqualToString:], which is clearly documented.
>
> What value does NSString's isEqualToString: bring to the table over its implementation of isEqual? Is it just a matter of foregoing an 'if ([obj isKindOfClass:[NSString class])' construct at the front end? Put another way, why does NSString provide isEqualToString: as a distinct method?
Exactly that, it's a little faster to avoid checking the class. It's a general style of Foundation to offer class-specific methods like this.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden