Lines Matching full:pcre2test
3 <title>pcre2test specification</title>
6 <h1>pcre2test man page</h1>
28 <li><a name="TOC13" href="#SEC13">DEFAULT OUTPUT FROM pcre2test</a>
40 <b>pcre2test [options] [input file [output file]]</b>
43 <b>pcre2test</b> is a test program for the PCRE2 regular expression libraries,
54 The input for <b>pcre2test</b> is a sequence of regular expression patterns and
66 program as <b>pcre2test</b>, with a cleaner modifier syntax. Nevertheless, there
78 <b>pcre2test</b> program can be used to test all the libraries. However, its own
91 Input to <b>pcre2test</b> is processed line by line, either by calling the C
101 characters in <b>pcre2test</b> input files. There is a facility for specifying
208 Do not output the version number of <b>pcre2test</b> at the start of execution.
244 If <b>pcre2test</b> is given two filename arguments, it reads from the first and
246 standard input. If <b>pcre2test</b> is given only one argument, it reads from
251 When <b>pcre2test</b> is built, a configuration option can specify that it
267 When the input is a terminal, <b>pcre2test</b> prompts for each line of input,
358 of the modifiers are specific to <b>pcre2test</b>, and should not be used in
432 pcre2test to read the next line as a continuation of the regular expression.
663 Normally, <b>pcre2test</b> passes a context block to <b>pcre2_compile()</b>. If
690 By default, <b>pcre2test</b> passes patterns as zero-terminated strings to
829 The default for the library is set when PCRE2 is built, but <b>pcre2test</b>
846 The <b>/posix</b> and <b>posix_nosub</b> modifiers cause <b>pcre2test</b> to call
940 pushed onto a stack of compiled patterns, and <b>pcre2test</b> expects the next
1043 the subject string that matched the entire pattern, <b>pcre2test</b> should in
1100 A callout function is supplied when <b>pcre2test</b> calls the library matching
1116 used as a return from <b>pcre2test</b>'s callout function.
1179 Unlike subject strings, <b>pcre2test</b> does not process replacement strings
1227 size of buffer that is required. When this happens, <b>pcre2test</b> shows the
1261 If the <b>find_limits</b> modifier is present, <b>pcre2test</b> calls
1287 returned for a match, non-match, or partial match, <b>pcre2test</b> shows it.
1295 The <b>memory</b> modifier causes <b>pcre2test</b> to log all memory allocation
1351 Normally, <b>pcre2test</b> passes a context block to <b>pcre2_match()</b>,
1360 By default, <b>pcre2test</b> uses the standard PCRE2 matching function,
1374 <br><a name="SEC13" href="#TOC1">DEFAULT OUTPUT FROM pcre2test</a><br>
1380 When a match succeeds, <b>pcre2test</b> outputs the list of captured substrings,
1390 For any other return, <b>pcre2test</b> outputs the PCRE2 negative error number
1393 an example of an interactive <b>pcre2test</b> run.
1395 $ pcre2test
1406 shown by <b>pcre2test</b> unless the <b>allcaptures</b> modifier is specified. In
1514 If the pattern contains any callout requests, <b>pcre2test</b>'s callout
1519 The callout function in <b>pcre2test</b> returns zero (carry on matching) by
1524 Inserting callouts can be helpful when using <b>pcre2test</b> to check
1609 When <b>pcre2test</b> is outputting text in the compiled version of a pattern,
1614 When <b>pcre2test</b> is outputting text that is a matched part of a subject
1636 documentation. In this section we describe the features of <b>pcre2test</b> that
1641 onto a stack of compiled patterns, and <b>pcre2test</b> expects the next line to
