| 1 |
News about PCRE releases |
News about PCRE releases |
| 2 |
------------------------ |
------------------------ |
| 3 |
|
|
| 4 |
|
Release 7.0 23-Nov-06 |
| 5 |
|
--------------------- |
| 6 |
|
|
| 7 |
|
This release has a new major number because there have been some internal |
| 8 |
|
upheavals to facilitate the addition of new optimizations and other facilities, |
| 9 |
|
and to make subsequent maintenance and extension easier. Compilation is likely |
| 10 |
|
to be a bit slower, but there should be no major effect on runtime performance. |
| 11 |
|
Previously compiled patterns are NOT upwards compatible with this release. If |
| 12 |
|
you have saved compiled patterns from a previous release, you will have to |
| 13 |
|
re-compile them. Important changes that are visible to users are: |
| 14 |
|
|
| 15 |
|
1. The Unicode property tables have been updated to Unicode 5.0.0, which adds |
| 16 |
|
some more scripts. |
| 17 |
|
|
| 18 |
|
2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline |
| 19 |
|
sequence as a newline. |
| 20 |
|
|
| 21 |
|
3. The \R escape matches a single Unicode newline sequence as a single unit. |
| 22 |
|
|
| 23 |
|
4. New features that will appear in Perl 5.10 are now in PCRE. These include |
| 24 |
|
alternative Perl syntax for named parentheses, and Perl syntax for |
| 25 |
|
recursion. |
| 26 |
|
|
| 27 |
|
5. The C++ wrapper interface has been extended by the addition of a |
| 28 |
|
QuoteMeta function and the ability to allow copy construction and |
| 29 |
|
assignment. |
| 30 |
|
|
| 31 |
|
For a complete list of changes, see the ChangeLog file. |
| 32 |
|
|
| 33 |
|
|
| 34 |
|
Release 6.7 04-Jul-06 |
| 35 |
|
--------------------- |
| 36 |
|
|
| 37 |
|
The main additions to this release are the ability to use the same name for |
| 38 |
|
multiple sets of parentheses, and support for CRLF line endings in both the |
| 39 |
|
library and pcregrep (and in pcretest for testing). |
| 40 |
|
|
| 41 |
|
Thanks to Ian Taylor, the stack usage for many kinds of pattern has been |
| 42 |
|
significantly reduced for certain subject strings. |
| 43 |
|
|
| 44 |
|
|
| 45 |
|
Release 6.5 01-Feb-06 |
| 46 |
|
--------------------- |
| 47 |
|
|
| 48 |
|
Important changes in this release: |
| 49 |
|
|
| 50 |
|
1. A number of new features have been added to pcregrep. |
| 51 |
|
|
| 52 |
|
2. The Unicode property tables have been updated to Unicode 4.1.0, and the |
| 53 |
|
supported properties have been extended with script names such as "Arabic", |
| 54 |
|
and the derived properties "Any" and "L&". This has necessitated a change to |
| 55 |
|
the interal format of compiled patterns. Any saved compiled patterns that |
| 56 |
|
use \p or \P must be recompiled. |
| 57 |
|
|
| 58 |
|
3. The specification of recursion in patterns has been changed so that all |
| 59 |
|
recursive subpatterns are automatically treated as atomic groups. Thus, for |
| 60 |
|
example, (?R) is treated as if it were (?>(?R)). This is necessary because |
| 61 |
|
otherwise there are situations where recursion does not work. |
| 62 |
|
|
| 63 |
|
See the ChangeLog for a complete list of changes, which include a number of bug |
| 64 |
|
fixes and tidies. |
| 65 |
|
|
| 66 |
|
|
| 67 |
|
Release 6.0 07-Jun-05 |
| 68 |
|
--------------------- |
| 69 |
|
|
| 70 |
|
The release number has been increased to 6.0 because of the addition of several |
| 71 |
|
major new pieces of functionality. |
| 72 |
|
|
| 73 |
|
A new function, pcre_dfa_exec(), which implements pattern matching using a DFA |
| 74 |
|
algorithm, has been added. This has a number of advantages for certain cases, |
| 75 |
|
though it does run more slowly, and lacks the ability to capture substrings. On |
| 76 |
|
the other hand, it does find all matches, not just the first, and it works |
| 77 |
|
better for partial matching. The pcrematching man page discusses the |
| 78 |
|
differences. |
| 79 |
|
|
| 80 |
|
The pcretest program has been enhanced so that it can make use of the new |
| 81 |
|
pcre_dfa_exec() matching function and the extra features it provides. |
| 82 |
|
|
| 83 |
|
The distribution now includes a C++ wrapper library. This is built |
| 84 |
|
automatically if a C++ compiler is found. The pcrecpp man page discusses this |
| 85 |
|
interface. |
| 86 |
|
|
| 87 |
|
The code itself has been re-organized into many more files, one for each |
| 88 |
|
function, so it no longer requires everything to be linked in when static |
| 89 |
|
linkage is used. As a consequence, some internal functions have had to have |
| 90 |
|
their names exposed. These functions all have names starting with _pcre_. They |
| 91 |
|
are undocumented, and are not intended for use by outside callers. |
| 92 |
|
|
| 93 |
|
The pcregrep program has been enhanced with new functionality such as |
| 94 |
|
multiline-matching and options for output more matching context. See the |
| 95 |
|
ChangeLog for a complete list of changes to the library and the utility |
| 96 |
|
programs. |
| 97 |
|
|
| 98 |
|
|
| 99 |
|
Release 5.0 13-Sep-04 |
| 100 |
|
--------------------- |
| 101 |
|
|
| 102 |
|
The licence under which PCRE is released has been changed to the more |
| 103 |
|
conventional "BSD" licence. |
| 104 |
|
|
| 105 |
|
In the code, some bugs have been fixed, and there are also some major changes |
| 106 |
|
in this release (which is why I've increased the number to 5.0). Some changes |
| 107 |
|
are internal rearrangements, and some provide a number of new facilities. The |
| 108 |
|
new features are: |
| 109 |
|
|
| 110 |
|
1. There's an "automatic callout" feature that inserts callouts before every |
| 111 |
|
item in the regex, and there's a new callout field that gives the position |
| 112 |
|
in the pattern - useful for debugging and tracing. |
| 113 |
|
|
| 114 |
|
2. The extra_data structure can now be used to pass in a set of character |
| 115 |
|
tables at exec time. This is useful if compiled regex are saved and re-used |
| 116 |
|
at a later time when the tables may not be at the same address. If the |
| 117 |
|
default internal tables are used, the pointer saved with the compiled |
| 118 |
|
pattern is now set to NULL, which means that you don't need to do anything |
| 119 |
|
special unless you are using custom tables. |
| 120 |
|
|
| 121 |
|
3. It is possible, with some restrictions on the content of the regex, to |
| 122 |
|
request "partial" matching. A special return code is given if all of the |
| 123 |
|
subject string matched part of the regex. This could be useful for testing |
| 124 |
|
an input field as it is being typed. |
| 125 |
|
|
| 126 |
|
4. There is now some optional support for Unicode character properties, which |
| 127 |
|
means that the patterns items such as \p{Lu} and \X can now be used. Only |
| 128 |
|
the general category properties are supported. If PCRE is compiled with this |
| 129 |
|
support, an additional 90K data structure is include, which increases the |
| 130 |
|
size of the library dramatically. |
| 131 |
|
|
| 132 |
|
5. There is support for saving compiled patterns and re-using them later. |
| 133 |
|
|
| 134 |
|
6. There is support for running regular expressions that were compiled on a |
| 135 |
|
different host with the opposite endianness. |
| 136 |
|
|
| 137 |
|
7. The pcretest program has been extended to accommodate the new features. |
| 138 |
|
|
| 139 |
|
The main internal rearrangement is that sequences of literal characters are no |
| 140 |
|
longer handled as strings. Instead, each character is handled on its own. This |
| 141 |
|
makes some UTF-8 handling easier, and makes the support of partial matching |
| 142 |
|
possible. Compiled patterns containing long literal strings will be larger as a |
| 143 |
|
result of this change; I hope that performance will not be much affected. |
| 144 |
|
|
| 145 |
|
|
| 146 |
|
Release 4.5 01-Dec-03 |
| 147 |
|
--------------------- |
| 148 |
|
|
| 149 |
|
Again mainly a bug-fix and tidying release, with only a couple of new features: |
| 150 |
|
|
| 151 |
|
1. It's possible now to compile PCRE so that it does not use recursive |
| 152 |
|
function calls when matching. Instead it gets memory from the heap. This slows |
| 153 |
|
things down, but may be necessary on systems with limited stacks. |
| 154 |
|
|
| 155 |
|
2. UTF-8 string checking has been tightened to reject overlong sequences and to |
| 156 |
|
check that a starting offset points to the start of a character. Failure of the |
| 157 |
|
latter returns a new error code: PCRE_ERROR_BADUTF8_OFFSET. |
| 158 |
|
|
| 159 |
|
3. PCRE can now be compiled for systems that use EBCDIC code. |
| 160 |
|
|
| 161 |
|
|
| 162 |
Release 4.4 21-Aug-03 |
Release 4.4 21-Aug-03 |
| 163 |
--------------------- |
--------------------- |
| 164 |
|
|
Parent Directory
| 
Revision Log
| 
Patch