Consider the pattern:
[[thing description] isEqualToString: someString];
All objects will return a string for description. Whether it is
meaningful in your terms is a whole other issue.
NSNumber will return a sensible numeric string.
NSString will return itself.
Generally, property-list objects (other than NSData) will return
something generically useful in response to -description.
Note the NSStringFrom... functions for converting points, ranges, etc
into strings and back again.
It is a good discipline to stick to property list objects for files
when reasonable.
Also note that -[NSString rangeOfString:options] can be wrapped in a
category on NSString to provide a handy -[NSString compare].
@implementation NSString (contains)
- (BOOL) contains:(NSString *) s
{ // loose compare
return [self rangeOfString: s options:
NSCaseInsensitiveSearch].location != NSNotFound;
}
- (BOOL) containsPrecisely:(NSString *) s
{ // exact compare
return [self rangeOfString: s options: NSLiteralSearch].location !=
NSNotFound;
}
@end
_______________________________________________
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 arch...@mail-archive.com
