nanaxmet.blogg.se - Xojo classes examples

#Xojo classes examples for mac
#Xojo classes examples code
#Xojo classes examples plus
#Xojo classes examples windows

#Xojo classes examples windows

PCRE supports only option 4, which often confuses Windows developers since it causes test $ to fail against test\r\n as Windows uses \r\n for line breaks. This option is actually a modification to the PCRE library made in Xojo. I recommend you leave this option as zero, which is most likely to give you the results you intended.

#Xojo classes examples for mac

Set it to 2 for Mac (\r), 3 for Windows (\n) and 4 for UNIX (\n). Set it to 1 to use auto-detect the host platform, and use \n when your application runs on Windows and Linux, and \r when it runs on a Mac. The default is 0, which accepts both \r and \n as end-of-line characters. This option affect which character the caret and dollar treat as the “end of line” character. The LineEndType option is the only one that takes an Integer instead of a Boolean.

#Xojo classes examples code

This way, somebody reading your source code will clearly see when you’re using greedy quantifiers and when you’re using lazy quantifiers when they look only at the regular expression. I strongly recommend against setting Greedy to False.

Set Greedy (True by default) to False if you want quantifiers to be lazy, effectively making.

This option is the equivalent of “single line mode” or /s in other programming languages.

Set DotMatchAll (False by default) to True to make the dot match all characters, including line break characters.

This option is the inverse of “case insensitive mode” or /i in other programming languages.

Set CaseSensitive (False by default) to True to treat uppercase and lowercase letters as different characters.

The RegExOptions class has nine properties to set various options for your regular expression. SubExpressionStartB returns the byte offset of the start of the match of the whole regex or one of the capturing groups depending on the numeric index you pass as a parameter to the property. SubExpressionString(0) returns the whole regex match, while SubExpressionString(1) through SubExpressionString(SubExpressionCount-1) return the matches of the capturing group. The SubExpressionString property returns the substring matched by the regular expression or a capturing group.

#Xojo classes examples plus

The SubExpressionCount property returns the number of capturing groups in the regular expression plus one. When the Regex.Search method finds a match, it stores the match’s details in a RegExMatch object. Keep calling Search without any parameters until it returns Nil to iterate over all regular expression matches in the string. Do not pass the subject string again, since doing so restarts the search from the beginning of the string. To find the second match in the same subject string, call the Search method again, without any parameters. This method returns an instance of the RegExMatch class if a match is found, or Nil if no match is found. To check if a regular expression matches a particular string, call the Search method of the RegEx object, and pass the subject string as a parameter. You can set various options in the Options property, which is an instance of the RegExOptions class. Assign your regular expression to the SearchPattern property. To use a regular expression, you need to create a new instance of the RegEx class. You’ll also need to use the TextConverter to convert the strings returned by the RegEx class from UTF-8 back into the encoding your application is working with. This means that if you want to process non-ASCII data that you’ve retrieved from a file or the network, you’ll need to use Xojo’s TextConverter class to convert your strings into UTF-8 before passing them to the RegEx object. In PCRE, they’re off by default, while in Xojo they’re on by default. The only exception are the case insensitive and “multi-line” matching modes. Everything said in the tutorial about PCRE’s regex flavor also applies to Xojo. The regular expressions tutorial on this website does not explicitly mention Xojo. What this means to you as a Xojo developer is that the RegEx class provides you with a rich flavor of Perl-compatible regular expressions. Internally, this class is based on the open source PCRE library. Xojo, formerly known as REALbasic, includes a built-in RegEx class. How to Use Regular Expressions in Xojo (REALbasic)