Lines Matching refs:ACCEPT

1503     SSize_t stopmin = OPTIMIZE_INFTY; /* min length accounting for ACCEPT
1505                                          an ACCEPT */
3387             if (OP(scan)==ACCEPT) {
3388                 /* m{(*ACCEPT)x} does not have to start with 'x' */
3623     /* deal with (*ACCEPT), Eg, consider /(foo(*ACCEPT)|bop)bar/ */
3627         match while *ignoring* the implication of ACCEPT, and 'delta'
3637         of ACCEPT the only opcode that signaled acceptance was the END
3639         ACCEPT is thus conceptually an early successful return out of
3642         "current min" if necessary when an ACCEPT opcode is encountered.
3644         Thus stopmin might be smaller than min if we saw an (*ACCEPT),
3647         match can be computed as min(A)+min(B). But (*ACCEPT) means
3651              A  = /(foo(*ACCEPT)|x+)/
3653              AB = /(foo(*ACCEPT)|x+)whop/
3658         stopmin would be OPTIMIZE_INFTY as it does not contain an ACCEPT.
3664         In something like /(dude(*ACCEPT)|irk)x{3,7}/ we would have a
3670         fragment /(x{10,20}(*ACCEPT)|a)b+/, we would have a min of 2,
3672         the ACCEPT doesn't reduce the minimum length of the string that
3675         In something like /foo(*ACCEPT)ba?r/ we would have a min of 5
3679         possible. ACCEPT affects some aspects of the optimizer, like
3687         ACCEPT, causing its callers to treat the returned min as a
3688         stopmin as the recursion unwinds. Thus a single ACCEPT can affect