Re: Something strange in the NSString documentation
Re: Something strange in the NSString documentation
- Subject: Re: Something strange in the NSString documentation
- From: Stephane Sudre <email@hidden>
- Date: Fri, 19 Aug 2005 16:15:03 +0200
On 19 août 05, at 15:18, Jack Nutting wrote:
On 8/19/05, Stephane Sudre <email@hidden> wrote:
The strange point is the link to -compare:options:range:.
The way I understand how the compare:options:range method is working
"compared" to the rangeOfString;options: API and the way the
documentation is presenting things, I would tend to believe that the
link shall be to the -rangeOfString;options: instead.
For instance, if I want to check if a string has a suffix with an
insensitive case search, the shortest code (with the smallest number
of
arguments) could look like this:
- (BOOL) hasCaseInsensitiveSuffix:(NSString *) inSuffix
{
NSRange tRange;
tRange=[self rangeOfString: inSuffix options:
NSCaseInsensitiveSearch+NSBackwardsSearch+NSAnchoredSearch];
return (tRange.location!=NSNotFound)
}
That may be the shortest code, but it can also be terribly
inefficient, depending on the size of your string, since it will
search backwards through the *entire*string*.
I would tend to believe it won't since there is the NSAnchoredSearch
option.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden