#Xojo newline code

wxRE_ICASE makes the regular expression case insensitive. You can set three other flags in addition to the flavor.

#Xojo newline code

The only reason to use the ERE flavor is when your code has to work when wxWidgets is compiled without the вЂњbuilt-inвЂќ regular expression library (i.e. Every valid ERE is also a valid ARE, and will give identical results. I recommend you always specify the wxRE_ADVANCED flag. If you specify a flavor, wxRE_EXTENDED is the default. To set the regex flavor, specify one of the flags wxRE_EXTENDED, wxRE_ADVANCED or wxRE_BASIC. The second parameter allows you to set certain matching options.

Pass your regular expression as a string as the first parameter.

Doing so will simply replace the regular expression held by the wxRegEx object. You can call this method on any wxRegEx object, including one that already holds a compiled regular expression. Check wxRegEx::IsValid to determine if the regular expression was compiled successfully.Д«ool wxRegEx::Compile(const wxString& pattern, int flags = wxRE_EXTENDED) compiles a regular expression. The constructor will always create the object, even if your regular expression is invalid. WxRegEx(const wxString& expr, int flags = wxRE_EXTENDED) creates a wxRegEx object with a compiled regular expression. wxRegEx::IsValid will return false until you do. Before you can use the object, you have to call wxRegEx::Compile(). To use the wxWidgets regex engine, you need to instantiate the wxRegEx class. The wxRegEx::Replace() method uses the same syntax for the replacement text as TclвЂ™s regsub command. Unlike in Tcl, EREs rather than the far more powerful AREs are the default. This means that wxWidgets supports the same three regular expressions flavors: Tcl Advanced Regular Expressions, POSIX Extended Regular Expressions and POSIX Basic Regular Expressions. WxWidgets uses the exact same regular expression engine that was developed by Henry Spencer for Tcl 8.2. WxWidgets Supports Three Regular Expression Flavors