Lines Matching refs:current
77 for the current position in the subject line was incorrect if it was after
216 current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
1949 AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
2008 to overrun the end of the current line. If another match was found, it was
2021 to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
2220 generating tables according to the current locale when PCRE is compiled. It
2346 called "current" as "current_branch", to prevent a collision with the
2863 (Perl fails the current match path).
2904 any errors with the current Unicode tables. Thanks to Peter Kankowski for
3320 "\r\nA" because change 7.0/46 below moves the current point on by two
3365 (d) \K resets the start of the current match so that everything before
3436 makevp.bat for the current PCRE, using the additional files
3611 line is "zero bytes in current character"), it caused compiler complaints.
4213 made were to insert the current release number. This seemed silly, because
4661 what's available on my current Linux desktop machine.
4996 the current level for patterns like /(b+(?U)a+)/. It did apply to parenthesized
5000 14. PCRE now supports the \G assertion. It is true when the current matching
5075 matching continues; if it returns a non-zero value, the match at the current
5081 the match and the current position in the text. There are some new data escapes
5084 \C+ in addition, show current contents of captured substrings
5187 The current list of available information is:
5743 to character tables built by pcre_maketables() in the current locale. If NULL
