Lines Matching refs:order
467 Search order: first, last, middle.
640 same name now checks them in the order in which they appear in the pattern.
1916 negative or greater than the length of the string. In order to test this,
1935 loops, in order to improve performance in some environments. At the same
2360 20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
2383 length of subject string that was needed in order to match a given pattern.
2488 nothing is needed in order to break the loop.
3229 are not scanned in any specific order and on different systems the order
3269 order to be able to cut out the UTF-8 tables in the latter when UTF-8
3470 that made a preliminary scan of the pattern in order to do this. That was
3646 1. In order to handle tests when input lines are enormously long, pcretest has
3707 now limited to 30,000 bytes in order to prevent this.
3883 In order to prevent this happening, the specification of recursion has
3922 "configure" and the latter not, in order to fix a problem somebody had
4121 6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
4188 5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
4463 pcre_stack_free, are used. They are always called in strict stacking order,
4712 be tidied up in order to avoid warnings.
4954 name, zero terminated. The names are in alphabetical order.
5033 order to support additional features. One way would have been to define
5185 bytes in the wrong order. How dumb can you get?
5371 pattern, which is not what we want. Replace // by /(?#)/ in order to avoid this
5538 2. Put dummy code into study.c in order to trick the optimizer of the IBM C
5774 fixed one that was wrong - it said "range out of order" when it meant "invalid
5798 the offsets during matching if necessary, in order to ensure that
