Lines Matching refs:K

247     (a) A crash if /K and /F were both set with the option to save the compiled
325 36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
459 4. A pattern such as (?=ab\K) that uses \K in an assertion can set the start
496 and there is no \K in the pattern. JIT should avoid empty match checks in
525 16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
744 38. The use of \K (reset reported match start) within a repeated possessive
1769 8K to 20K. (The actual buffer used is three times this size.)
1777 (d) Numerical values in pcregrep options can be followed by K or M, for
1778 example --buffer-size=50K.
2094 10. \K gave a compile-time error if it appeared in a lookbehind assersion.
2096 11. \K was not working if it appeared in an atomic group or in a group that
2098 \K is "not well defined" if used in an assertion. PCRE now accepts it if
2285 is correctly used as a library, but I received one complaint about 50K of
2326 starts with a lookbehind assertion or \b or \B (\K is not supported by
2361 /g option in pcretest when the pattern contains \K, which makes it possible
3179 (d) \K resets the start of the current match so that everything before
3270 support is not required. This saves 1.5-2K of code, which is important in
3466 than about 50K.
3649 default size has been increased from 32K to 50K.
4219 8K, or the rest of the document (whichever is the shorter) is available
4220 for matching (and similarly the previous 8K for lookbehind assertions).
4387 support. It adds about 90K to the size of the library. The meanings of the
4527 13. In pcretest, the buffer for reading a data line was set at 30K, but the
4912 32. The default maximum size of a compiled pattern is 64K. There have been a