Comments on: Does a NSString contain a substring ?

By: Una stringa contiene un’altra stringa? | iOS Dev Blog

Una stringa contiene un’altra stringa? | iOS Dev Blog — Sun, 25 Mar 2012 20:32:06 +0000

[...] controllare se una data stringa ne contiene un’altra, è sufficiente usare il seguente snippet: 1 2 3 4 5 6 7 8 9 10 11 12 13 NSRange textRange; textRange =[string [...]

By: ym

ym — Tue, 02 Aug 2011 16:02:01 +0000

THANKS for your solution. It works like magic

By: Jorge Ramirez

Jorge Ramirez — Sat, 12 Mar 2011 21:33:25 +0000

…solved… had something to do with compiler optimizations in release config mode, the function works great.

By: Jorge Ramirez

Jorge Ramirez — Sat, 12 Mar 2011 21:09:21 +0000

I used your function and it worked great under Debug configuration, but once on Release Configuration, fails to read NSRange .. debug console ouputs:

Unable to access variable “range”

any Idea?

By: Spencer MacDonald

Spencer MacDonald — Fri, 19 Feb 2010 19:51:46 +0000

Hi Susan

Something like the following (as a category on NSString):

- (BOOL)doesContainSubstring:(NSString *)substring{

//If self or substring have 0 length they cannot match
//This can have odd results with NSRange
if([self length] == 0 || [substring length] == 0)
return NO;

NSRange textRange;

textRange = [[self lowercaseString] rangeOfString:[substring lowercaseString]];

if(textRange.location != NSNotFound)
{
return YES;
}else{
return NO;
}

}

By: Susan

Susan — Fri, 19 Feb 2010 05:11:38 +0000

I’ll use that code A LOT.

How would I make it into a Category and just make it a part of NSString everywhere?

By: Robert

Robert — Tue, 09 Feb 2010 14:15:47 +0000

You posted this 10 months ago and it’s still helping people. Thanks for the information.

By: jose

jose — Sun, 20 Dec 2009 15:11:41 +0000

@frank, you need to chill dawg. just because you dont like (or know) something doesnt mean it sucks. different strokes for different folks.

By: Spencer MacDonald

Spencer MacDonald — Wed, 16 Sep 2009 18:34:56 +0000

To say it is a bit messed up is a bit extreme

Its different, and I expect a lot of people prefer it to C/C++, myself included.

By: frankSinatra

frankSinatra — Wed, 16 Sep 2009 18:01:00 +0000

crisbetewsky, pity!what pity! probably because Obj-C sucks big time. People in Apple are so stupid not to use just C/C++ instead of this messed up language obj-C. (-) (+) before function call waiting for some typos and headaches.