nsregularexpression

There is a clever 1st answer given here for splitting swift string with a regex expression split string answer However it keeps the searched text within the array of answers. I'm trying to do a similar thing, but ignoring the characters acting as separators (e.g. just like the swift split function, but just with a regex expression as the separator). As an example: regex would be something like "\\\||Z|ZY" and when applied to string of "hi|thisZshouldZYbe|separated" then you would get back an array ["hi", "this", "should", "be", "separated"] NB. The regex is adapted to the swift

As the title states, I wonder if NSRegularExpression in both Objective-c or Swift, support partial case insensitive search? Namely, will the pattern recognize (?ismx)? If not, is there a brief reason for this inability? I truly appreciate your explanation. From the NSRegularExpression Class Reference : Table 2 Regular Expression Operators ... (?ismwx-ismwx:...) Flag settings. Evaluate the parenthesized expression with the specified flags enabled or -disabled. ... (?ismwx-ismwx) Flag settings. Change the flag settings. Changes apply to the portion of the pattern following the setting. For

I'm trying to do a simple regex match using NSRegularExpression, but I'm having some problems matching the string when the source contains multibyte characters: let string = "D 9" // The following matches (any characters)(SPACE)(numbers)(any characters) let pattern = "([\\s\\S]*) ([0-9]*)(.*)" let slen : Int = string.lengthOfBytesUsingEncoding(NSUTF8StringEncoding) var error: NSError? = nil var regex = NSRegularExpression(pattern: pattern, options: NSRegularExpressionOptions.DotMatchesLineSeparators, error: &error) var result = regex?.stringByReplacingMatchesInString(string, options: nil,

Apple says that NSRegularExpression is based on the ICU Regular Expression library: https://developer.apple.com/library/ios/documentation/Foundation/Reference/NSRegularExpression_Class/ The pattern syntax currently supported is that specified by ICU. The ICU regular expressions are described at http://userguide.icu-project.org/strings/regexp . That page (on icu-project.org) claims that Named Capture Groups are now supported, using the same syntax as .NET Regular Expressions: (?<name>...) Named capture group. The <angle brackets> are literal - they appear in the pattern. I have written a

I'm using the following regex expression to detect hashtags and mentions in my app. NSRegularExpression *regex = [NSRegularExpression regularExpressionWithPattern:@"(#|@)(\\w+)" options:NSRegularExpressionCaseInsensitive error:&error]; However users within my app are allowed to use some special characters in their usernames. For example @user.name or @user_name . Spaces are not allowed. However using thins regular expression would only detect @user when it should in fact be @user.name . Hostages work perfectly but the special characters in usernames break the mention functionality. I'm really

My goal is to store the information for an attributed string in Parse.com. I decided to come up with an encoding for attributed text for my images that works by replacing any string {X} in braces with the corresponding image. For example: Picture of 2 colorless mana: {X} Should produce an attributed string where {X} is replaced by an image. This is what I've tried: NSString *formattedText = @"This will cost {2}{PW}{PW} to cast."; NSRegularExpression *regex = [NSRegularExpression regularExpressionWithPattern:@"(?<=\\{)[^}]+(?=\\})" options:NSRegularExpressionAnchorsMatchLines error:nil];

I have an input string that looks something like this: HLI6Ch60000Ch500C0Ch46400Ch30000Ch21888Ch10E79CS07LCU3Ch37880Ch27800Ch16480CS8CA00000000000000000000 Now I don't care about the part that follows the last letter A , it'll always be A and exactly 20 numbers that are of no use to me. I do, however, need the part before the last letter A , and ideally, I'd need it to be separated into two different captures, just like this: 1: HLI6Ch60000Ch500C0Ch46400Ch30000Ch21888Ch10E79CS07 2: LCU3Ch37880Ch27800Ch16480CS8C The only way to identify these matches is that they end with characters CS followed