Lines Matching refs:g
16 2. Quantification of certain items (e.g. atomic back references) could cause
27 /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
117 30. Error messages for syntax errors following \g and \k were giving inaccurate
280 is converted to (*FAIL). E.g: /(?(?!))/.
326 (e.g. /(?<=\Ka)/) could make pcregrep loop.
330 38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
433 example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
471 above a certain threshold (e.g: 256). The only limitation is that the value
603 that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
609 have the modifier quality were involved, e.g. Hangul syllables.
981 (g) In a Windows environment, the default for -d has been changed from
1005 explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
1348 repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1557 in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
1728 36. \g was being checked for fancy things in a character class, when it should
1729 just be a literal "g".
1872 If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1897 13. Imitating Perl's /g action for multiple matches is tricky when the pattern
2018 15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
2067 4. On systems that do not have stdint.h (e.g. Solaris), check for and include
2320 "g". If the first part-match was for the string "dog", restarting with
2361 /g option in pcretest when the pattern contains \K, which makes it possible
2586 after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
2588 no match. To help with detecting such bugs (e.g. with valgrind), I modified
2659 11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
2660 which, however, unlike Perl's \g{...}, are subroutine calls, not back
2998 when the subject happened to end in the byte 0x85 (e.g. if the last
3104 expression for various reasons (e.g. to see if it's fixed length for look
3122 characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
3156 3. Add code to configure.ac to remove -g from the CFLAGS default settings.
3184 (f) \g{name} is another synonym - part of Perl 5.10's unification of
3187 (g) (?| introduces a group in which the numbering of parentheses in each
3348 19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
3350 was because its rules for how to advance for /g after matching an empty
3542 returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
3584 (g) The escape \gN or \g{N} has been added, where N is a positive or
3661 because it contains high-valued characters or Unicode property items, e.g.
3860 (g) Added the -H (--with-filename) option.
4122 versions of gcc, e.g. 2.95.4.
4231 (g) -- can be used to terminate pcregrep options if the next thing isn't an
4246 different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
4517 11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
4697 and 255 (e.g. /[\xFF]/) caused PCRE to crash.
4731 Problem: the scan can take a lot of time if the subject is very long (e.g.
4816 starting offset is non-zero. Used with the /g option of pcretest (or similar
4817 code), it works in the same way as it does for Perl's /g option. If all
4829 POSIX classes only within a class (e.g. /[[:alpha:]]/).
4846 contained both POSIX named classes and other characters, e.g. /[[:space:]abc/.
5124 match if the class was a negative one (e.g. [^ab]). This has been fixed.
5157 55. Unknown escapes inside character classes (e.g. [\M]) and escapes that
5158 aren't interpreted therein (e.g. [\C]) are literals in Perl. This is now also
5319 2. The pcretest program was not imitating Perl correctly for the pattern /a*/g
5364 2. Add support for the /g modifier to perltest.
5366 3. Fix pcretest so that it behaves even more like Perl for /g when the pattern
5411 2. pcretest was not making use of PCRE_NOTEMPTY when repeating for /g and /G,
5445 7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
5475 /g loops for multiple occurrences, using the new startoffset argument
5611 value of one (e.g. [^x]{1,6} ) was not compiled correctly. This could lead to
5683 4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
5861 as Perl does (e.g. [-az] or [az-]).
5884 (e.g. /a{1,3}/) was broken (I mis-optimized it).
5915 a subpattern that had matched an empty string, e.g. /(a|)\1*/. It now does what
