ZelphirKaltstahl
/
guile-examples


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181
							<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>&lt;%GLibRegexCompileFlags&gt;: </title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.2">
<link rel="home" href="index.html" title="">
<link rel="up" href="ch01.html" title="GLib">
<link rel="prev" href="re51.html" title="&lt;GRegex&gt;">
<link rel="next" href="re53.html" title="&lt;%GLibRegexError&gt;">
<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><img src="up-insensitive.png" width="16" height="16" border="0"></td>
<td><a accesskey="p" href="re51.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="re53.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="id-1.1.53"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2>&lt;%GLibRegexCompileFlags&gt;</h2>
<p>&lt;%GLibRegexCompileFlags&gt;</p>
</div>
<div class="refsect1">
<a name="id-1.1.53.2"></a><h2>Description</h2>
<p>Flags specifying compile-time options.</p>
</div>
<div class="refsect1">
<a name="id-1.1.53.3"></a><h2>Members</h2>
<div class="refsect2">
<a name="id-1.1.53.3.2"></a><h3>caseless</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_CASELESS</code></span></em></p>
<p>Letters in the pattern match both upper- and
    lowercase letters. This option can be changed within a pattern
    by a "(?i)" option setting.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.3"></a><h3>multiline</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_MULTILINE</code></span></em></p>
<p>By default, GRegex treats the strings as consisting
    of a single line of characters (even if it actually contains
    newlines). The "start of line" metacharacter ("^") matches only
    at the start of the string, while the "end of line" metacharacter
    ("$") matches only at the end of the string, or before a terminating
    newline (unless <span class="type">G_REGEX_DOLLAR_ENDONLY</span> is set). When
    <span class="type">G_REGEX_MULTILINE</span> is set, the "start of line" and "end of line"
    constructs match immediately following or immediately before any
    newline in the string, respectively, as well as at the very start
    and end. This can be changed within a pattern by a "(?m)" option
    setting.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.4"></a><h3>dotall</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_DOTALL</code></span></em></p>
<p>A dot metacharacter (".") in the pattern matches all
    characters, including newlines. Without it, newlines are excluded.
    This option can be changed within a pattern by a ("?s") option setting.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.5"></a><h3>extended</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_EXTENDED</code></span></em></p>
<p>Whitespace data characters in the pattern are
    totally ignored except when escaped or inside a character class.
    Whitespace does not include the VT character (code 11). In addition,
    characters between an unescaped "#" outside a character class and
    the next newline character, inclusive, are also ignored. This can
    be changed within a pattern by a "(?x)" option setting.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.6"></a><h3>anchored</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_ANCHORED</code></span></em></p>
<p>The pattern is forced to be "anchored", that is,
    it is constrained to match only at the first matching point in the
    string that is being searched. This effect can also be achieved by
    appropriate constructs in the pattern itself such as the "^"
    metacharacter.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.7"></a><h3>dollar-endonly</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_DOLLAR_ENDONLY</code></span></em></p>
<p>A dollar metacharacter ("$") in the pattern
    matches only at the end of the string. Without this option, a
    dollar also matches immediately before the final character if
    it is a newline (but not before any other newlines). This option
    is ignored if <span class="type">G_REGEX_MULTILINE</span> is set.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.8"></a><h3>ungreedy</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_UNGREEDY</code></span></em></p>
<p>Inverts the "greediness" of the quantifiers so that
    they are not greedy by default, but become greedy if followed by "?".
    It can also be set by a "(?U)" option setting within the pattern.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.9"></a><h3>raw</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_RAW</code></span></em></p>
<p>Usually strings must be valid UTF-8 strings, using this
    flag they are considered as a raw sequence of bytes.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.10"></a><h3>no-auto-capture</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_NO_AUTO_CAPTURE</code></span></em></p>
<p>Disables the use of numbered capturing
    parentheses in the pattern. Any opening parenthesis that is not
    followed by "?" behaves as if it were followed by "?:" but named
    parentheses can still be used for capturing (and they acquire numbers
    in the usual way).</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.11"></a><h3>optimize</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_OPTIMIZE</code></span></em></p>
<p>Optimize the regular expression. If the pattern will
    be used many times, then it may be worth the effort to optimize it
    to improve the speed of matches.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.12"></a><h3>firstline</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_FIRSTLINE</code></span></em></p>
<p>Limits an unanchored pattern to match before (or at) the
    first newline. Since: 2.34</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.13"></a><h3>dupnames</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_DUPNAMES</code></span></em></p>
<p>Names used to identify capturing subpatterns need not
    be unique. This can be helpful for certain types of pattern when it
    is known that only one instance of the named subpattern can ever be
    matched.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.14"></a><h3>newline-cr</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_NEWLINE_CR</code></span></em></p>
<p>Usually any newline character or character sequence is
    recognized. If this option is set, the only recognized newline character
    is '\r'.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.15"></a><h3>newline-lf</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_NEWLINE_LF</code></span></em></p>
<p>Usually any newline character or character sequence is
    recognized. If this option is set, the only recognized newline character
    is '\n'.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.16"></a><h3>newline-crlf</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_NEWLINE_CRLF</code></span></em></p>
<p>Usually any newline character or character sequence is
    recognized. If this option is set, the only recognized newline character
    sequence is '\r\n'.</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.17"></a><h3>newline-anycrlf</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_NEWLINE_ANYCRLF</code></span></em></p>
<p>Usually any newline character or character sequence
    is recognized. If this option is set, the only recognized newline character
    sequences are '\r', '\n', and '\r\n'. Since: 2.34</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.18"></a><h3>bsr-anycrlf</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_BSR_ANYCRLF</code></span></em></p>
<p>Usually any newline character or character sequence
    is recognised. If this option is set, then "\R" only recognizes the newline
   characters '\r', '\n' and '\r\n'. Since: 2.34</p>
</div>
<div class="refsect2">
<a name="id-1.1.53.3.19"></a><h3>javascript-compat</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_REGEX_JAVASCRIPT_COMPAT</code></span></em></p>
<p>Changes behaviour so that it is compatible with
    JavaScript rather than PCRE. Since: 2.34</p>
</div>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.33.1</div>
</body>
</html>