Lines Matching refs:release
28 Starting with release 8.30, it is possible to compile two separate PCRE
35 Starting with release 8.32 it is possible to compile a third separate
55 correspond to Unicode release 6.2.0.
297 Starting with release 8.30, it is possible to compile a PCRE library
626 Starting with release 8.32, it is possible to compile a PCRE library
1650 16-bit strings (from release 8.30) and 32-bit strings (from release
1687 macros PCRE_MAJOR and PCRE_MINOR to contain the major and minor release
1714 From release 8.32 there is also a direct interface for JIT execution,
1751 string containing the version of PCRE and its date of release.
2461 the API for release 8.20. For earlier versions, the memory could be
2787 variable. From release 8.00, this always returns 1, because the
3530 that were not supported for partial matching. From release 8.00
4928 at release 5.10. In contrast to the other sequences, which match only
5152 (see below). Up to and including release 8.31, PCRE matched an ear-
5764 patterns. This feature was not added to Perl until release 5.10. Python
5765 had the feature earlier, and PCRE introduced it at release 4.0, using
6060 found its way into Perl at release 5.10.
6585 into Perl at release 5.10.
7575 As well as UTF-8 support, PCRE also supports UTF-16 (from release 8.30)
7576 and UTF-32 (from release 8.32), by means of two additional libraries.
7630 ing takes place. From release 7.3 of PCRE, the check is according the
7772 points that are case-equivalent. Up to and including PCRE release 8.31,
8119 could implement some clever idea which release the stack if it is not
8127 Especially on embedded sytems, it might be a good idea to release mem-
8430 used with all patterns. From release 8.00 onwards, the restrictions no
8502 From release 8.00, the standard matching functions can also be used to
8779 update to a new PCRE release, though not all updates actually require
