Copyright (C) 2000-2012 |
GNU Info (libc.info)Matching POSIX RegexpsMatching a Compiled POSIX Regular Expression -------------------------------------------- Once you have compiled a regular expression, as described in Note: POSIX Regexp Compilation, you can match it against strings using `regexec'. A match anywhere inside the string counts as success, unless the regular expression contains anchor characters (`^' or `$'). - Function: int regexec (regex_t *COMPILED, char *STRING, size_t NMATCH, regmatch_t MATCHPTR [], int EFLAGS) This function tries to match the compiled regular expression `*COMPILED' against STRING. `regexec' returns `0' if the regular expression matches; otherwise, it returns a nonzero value. See the table below for what nonzero values mean. You can use `regerror' to produce an error message string describing the reason for a nonzero value; see Note: Regexp Cleanup. The argument EFLAGS is a word of bit flags that enable various options. If you want to get information about what part of STRING actually matched the regular expression or its subexpressions, use the arguments MATCHPTR and NMATCH. Otherwise, pass `0' for NMATCH, and `NULL' for MATCHPTR. Note: Regexp Subexpressions. You must match the regular expression with the same set of current locales that were in effect when you compiled the regular expression. The function `regexec' accepts the following flags in the EFLAGS argument: `REG_NOTBOL' Do not regard the beginning of the specified string as the beginning of a line; more generally, don't make any assumptions about what text might precede it. `REG_NOTEOL' Do not regard the end of the specified string as the end of a line; more generally, don't make any assumptions about what text might follow it. Here are the possible nonzero values that `regexec' can return: `REG_NOMATCH' The pattern didn't match the string. This isn't really an error. `REG_ESPACE' `regexec' ran out of memory. automatically generated by info2www version 1.2.2.9 |