regex (see blob/2).
Defined Options are defined below. Please consult the PCRE
documentation for details.
anycrlf, \R only matches CR, LF or CRLF. If unicode,
\R matches all Unicode line endings.true, do caseless matching.true, $ not to match newline at endtrue, . matches anything including NLtrue, allow duplicate names for subpatternstrue, ignore white space and # commentstrue, PCRE extra features (not much use currently)true, force matching to be before newlinejavascript, JavaScript compatibilitytrue, ^ and $ match newlines within dataany, recognize any Unicode newline sequence,
if anycrlf (default), recognize CR, LF, and CRLF as newline
sequences, if cr, recognize CR, if lf, recognize
LF and finally if crlf recognize CRLF as newline.true, use Unicode properties for \d, \w, etc.true, invert greediness of quantifiersIn addition to the options above that directly map to pcre flags the following options are processed:
true, study the regular expression.Start-Length. Note
the we use Start-Length` rather than the more conventional
Start-End to allow for immediate use with sub_atom/5 and
sub_string/5.
The capture_type specifies the default for this pattern. The
interface supports a different type for each named group using
the syntax (?<name_T>...), where T is one of S (string),
A (atom), I (integer), F (float), N (number), T (term)
and R (range). In the current implementation I, F and N are
synonyms for T. Future versions may act different if the parsed
value is not of the requested numeric type.