-/* Expect some output from the subprocess. Match the output against
- * the PCRE regular expression.
- *
- * 'code', 'extra', 'options', 'ovector' and 'ovecsize' are passed
- * through to the pcre_exec function. See pcreapi(3).
- *
- * If you want to match multiple strings, you have to combine them
- * into a single regexp, eg. "([Pp]assword)|([Ll]ogin)|([Ff]ailed)".
- * Then examine ovector[2], ovector[4], ovector[6] to see if they
- * contain '>= 0' or '-1'. See the pcreapi(3) man page for further
- * information.
- *
- * 'code' may be NULL, which means we don't match against a regular
- * expression. This is useful if you just want to wait for EOF or
- * timeout.
- *
- * This can return:
- *
- * MEXP_MATCHED:
- * The input matched the regular expression. Use ovector
- * to find out what matched in the buffer (mexp_h->buffer).
- * MEXP_TIMEOUT:
- * No input matched before the timeout (mexp_h->timeout) was reached.
- * MEXP_EOF:
- * The subprocess closed the connection.
- * MEXP_ERROR:
- * There was a system call error (eg. from the read call). See errno.
- * MEXP_PCRE_ERROR
- * There was a pcre_exec error. *pcre_ret is set to the error code
- * (see pcreapi(3) for a list of PCRE_* error codes and what they mean).
- */
-extern enum mexp_status mexp_expect (mexp_h *h, const pcre *code,
- const pcre_extra *extra,
- int options, int *ovector, int ovecsize,
- int *pcre_ret);