Lines Matching full:re

62 These routines implement POSIX 1003.2 regular expressions (``RE''s);
66 compiles an RE written as a string into an internal form,
74 of an RE.
110 so the ``RE'' is a literal string.
146 This flag permits inclusion of NULs in the RE;
164 contains the number of parenthesized subexpressions within the RE
173 matches the compiled RE pointed to by
183 The RE must have been compiled by a previous invocation of
187 so a single compiled RE can be used simultaneously by multiple threads.
229 for a discussion of what is matched in situations where an RE or a
239 If REG_NOSUB was specified in the compilation of the RE,
276 was matched by the entire RE.
278 subexpressions within the RE;
284 parentheses in the RE, left to right.
287 exist in the RE (that is, \fIi\fR\ > \fIpreg\fR\->\fIre_nsub\fR)\(emhave both
294 (Note, as an example in particular, that when the RE `(b*)+' matches `bbb',
390 frees any dynamically-allocated storage associated with the compiled RE
395 is no longer a valid compiled RE
408 forbidden by the RE grammar.
417 Memory usage is approximately linear in RE size, and largely insensitive
418 to RE complexity, except for bounded repetitions.
419 See BUGS for one short RE using them
442 An empty string is not a legal RE.
505 is largely insensitive to RE complexity \fIexcept\fR that back
508 for keeping RE length under about 30 characters,
515 An RE like, say,