Lines Matching +full:non +full:- +full:empty

42 regcomp, regexec, regerror, regfree \- regular-expression library
70 transforms error codes from either into human-readable messages,
73 frees any dynamically-allocated storage used by the internal form
126 Compile for newline-sensitive matching.
169 fails, it returns a non-zero error code;
190 the NUL-terminated string pointed to by
223 Note that a non-zero \fIrm_so\fR does not imply REG_NOTBOL;
235 returns 0 for success and the non-zero code REG_NOMATCH for failure.
236 Other non-zero error codes may be returned in exceptional situations;
269 An empty substring is denoted by equal offsets,
270 both indicating the character following the empty substring.
287 exist in the RE (that is, \fIi\fR\ > \fIpreg\fR\->\fIre_nsub\fR)\(emhave both
291 set to \-1.
296 an infinite number of empty strings following the last `b',
318 maps a non-zero
324 to a human-readable, printable message.
327 is non-NULL,
344 places the NUL-terminated message into the buffer pointed to by
373 shall be non-NULL and the
390 frees any dynamically-allocated storage associated with the compiled RE
413 for a discussion of the definition of case-independent matching.
428 Equivalence classes cannot begin or end bracket-expression ranges.
439 i.e. an operand of `|' cannot be an empty subexpression.
440 An empty parenthesized subexpression, `()', is legal and matches an
441 empty (sub)string.
442 An empty string is not a legal RE.
457 Non-zero error codes from
478 REG_EMPTY	empty (sub)expression
480 REG_INVARG	invalid argument, e.g. negative-length string
494 The back-reference code is subtle and doubts linger about its correctness
535 The implementation of word-boundary matching is a bit of a kludge,
536 and bugs may lurk in combinations of word-boundary matching and anchoring.