Age | Commit message (Collapse) | Author |
|
|
|
|
|
It might return the return value of match_error(), which returns
(-1).
|
|
|
|
|
|
From Leandro Pereira (@lafp on twitter)
|
|
|
|
- add a counter for limiting the search for repetitor items ('*', '+',
'-' and '?')
- add test case for this new kind of error
|
|
- revert "normal" call to optimized-tail-call-recursion for '*', '?' and
'-'
- add a "pattern too complex" test to !singlematch() branch, so that it
is limited on call numbers.
|
|
- switch '*', '?' and '-' to normal call, in order to pass into "too
complex" check
- remove assert()
- on error, quit early
|
|
- there is no need to escape "%" with "%%" in error message
- corrects a comment
- add a check for error
|
|
an error could be setted in classend(). check and propagate it if any.
|
|
different semantics as we cannot just abort as Lua does. So we have
to check return values carefully and I missed a few in the transition.
Patch by Sebastien Marie
|
|
a panic when using a ")(" pattern.
Found by Sebastien Marie
|
|
implementation.
|