/[pcre]/code/trunk/NEWS
ViewVC logotype

Diff of /code/trunk/NEWS

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 53 by nigel, Sat Feb 24 21:39:42 2007 UTC revision 738 by ph10, Fri Oct 21 09:04:01 2011 UTC
# Line 1  Line 1 
1  News about PCRE releases  News about PCRE releases
2  ------------------------  ------------------------
3    
4    Release 8.20 21-Oct-2011
5    ------------------------
6    
7    The main change in this release is the inclusion of Zoltan Herczeg's
8    just-in-time compiler support, which can be accessed by building PCRE with
9    --enable-jit. Large performance benefits can be had in many situations. 8.20
10    also fixes an unfortunate bug that was introduced in 8.13 as well as tidying up
11    a number of infelicities and differences from Perl.
12    
13    
14    Release 8.13 16-Aug-2011
15    ------------------------
16    
17    This is mainly a bug-fix release. There has been a lot of internal refactoring.
18    The Unicode tables have been updated. The only new feature in the library is
19    the passing of *MARK information to callouts. Some additions have been made to
20    pcretest to make testing easier and more comprehensive. There is a new option
21    for pcregrep to adjust its internal buffer size.
22    
23    
24    Release 8.12 15-Jan-2011
25    ------------------------
26    
27    This release fixes some bugs in pcregrep, one of which caused the tests to fail
28    on 64-bit big-endian systems. There are no changes to the code of the library.
29    
30    
31    Release 8.11 10-Dec-2010
32    ------------------------
33    
34    A number of bugs in the library and in pcregrep have been fixed. As always, see
35    ChangeLog for details. The following are the non-bug-fix changes:
36    
37    . Added --match-limit and --recursion-limit to pcregrep.
38    
39    . Added an optional parentheses number to the -o and --only-matching options
40      of pcregrep.
41    
42    . Changed the way PCRE_PARTIAL_HARD affects the matching of $, \z, \Z, \b, and
43      \B.
44    
45    . Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
46      bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
47    
48    . Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
49      START_OPTIMIZE option, which is now allowed at compile time
50    
51    
52    Release 8.10 25-Jun-2010
53    ------------------------
54    
55    There are two major additions: support for (*MARK) and friends, and the option
56    PCRE_UCP, which changes the behaviour of \b, \d, \s, and \w (and their
57    opposites) so that they make use of Unicode properties. There are also a number
58    of lesser new features, and several bugs have been fixed. A new option,
59    --line-buffered, has been added to pcregrep, for use when it is connected to
60    pipes.
61    
62    
63    Release 8.02 19-Mar-2010
64    ------------------------
65    
66    Another bug-fix release.
67    
68    
69    Release 8.01 19-Jan-2010
70    ------------------------
71    
72    This is a bug-fix release. Several bugs in the code itself and some bugs and
73    infelicities in the build system have been fixed.
74    
75    
76    Release 8.00 19-Oct-09
77    ----------------------
78    
79    Bugs have been fixed in the library and in pcregrep. There are also some
80    enhancements. Restrictions on patterns used for partial matching have been
81    removed, extra information is given for partial matches, the partial matching
82    process has been improved, and an option to make a partial match override a
83    full match is available. The "study" process has been enhanced by finding a
84    lower bound matching length. Groups with duplicate numbers may now have
85    duplicated names without the use of PCRE_DUPNAMES. However, they may not have
86    different names. The documentation has been revised to reflect these changes.
87    The version number has been expanded to 3 digits as it is clear that the rate
88    of change is not slowing down.
89    
90    
91    Release 7.9 11-Apr-09
92    ---------------------
93    
94    Mostly bugfixes and tidies with just a couple of minor functional additions.
95    
96    
97    Release 7.8 05-Sep-08
98    ---------------------
99    
100    More bug fixes, plus a performance improvement in Unicode character property
101    lookup.
102    
103    
104    Release 7.7 07-May-08
105    ---------------------
106    
107    This is once again mainly a bug-fix release, but there are a couple of new
108    features.
109    
110    
111    Release 7.6 28-Jan-08
112    ---------------------
113    
114    The main reason for having this release so soon after 7.5 is because it fixes a
115    potential buffer overflow problem in pcre_compile() when run in UTF-8 mode. In
116    addition, the CMake configuration files have been brought up to date.
117    
118    
119    Release 7.5 10-Jan-08
120    ---------------------
121    
122    This is mainly a bug-fix release. However the ability to link pcregrep with
123    libz or libbz2 and the ability to link pcretest with libreadline have been
124    added. Also the --line-offsets and --file-offsets options were added to
125    pcregrep.
126    
127    
128    Release 7.4 21-Sep-07
129    ---------------------
130    
131    The only change of specification is the addition of options to control whether
132    \R matches any Unicode line ending (the default) or just CR, LF, and CRLF.
133    Otherwise, the changes are bug fixes and a refactoring to reduce the number of
134    relocations needed in a shared library. There have also been some documentation
135    updates, in particular, some more information about using CMake to build PCRE
136    has been added to the NON-UNIX-USE file.
137    
138    
139    Release 7.3 28-Aug-07
140    ---------------------
141    
142    Most changes are bug fixes. Some that are not:
143    
144    1. There is some support for Perl 5.10's experimental "backtracking control
145       verbs" such as (*PRUNE).
146    
147    2. UTF-8 checking is now as per RFC 3629 instead of RFC 2279; this is more
148       restrictive in the strings it accepts.
149    
150    3. Checking for potential integer overflow has been made more dynamic, and as a
151       consequence there is no longer a hard limit on the size of a subpattern that
152       has a limited repeat count.
153    
154    4. When CRLF is a valid line-ending sequence, pcre_exec() and pcre_dfa_exec()
155       no longer advance by two characters instead of one when an unanchored match
156       fails at CRLF if there are explicit CR or LF matches within the pattern.
157       This gets rid of some anomalous effects that previously occurred.
158    
159    5. Some PCRE-specific settings for varying the newline options at the start of
160       a pattern have been added.
161    
162    
163    Release 7.2 19-Jun-07
164    ---------------------
165    
166    WARNING: saved patterns that were compiled by earlier versions of PCRE must be
167    recompiled for use with 7.2 (necessitated by the addition of \K, \h, \H, \v,
168    and \V).
169    
170    Correction to the notes for 7.1: the note about shared libraries for Windows is
171    wrong. Previously, three libraries were built, but each could function
172    independently. For example, the pcreposix library also included all the
173    functions from the basic pcre library. The change is that the three libraries
174    are no longer independent. They are like the Unix libraries. To use the
175    pcreposix functions, for example, you need to link with both the pcreposix and
176    the basic pcre library.
177    
178    Some more features from Perl 5.10 have been added:
179    
180      (?-n) and (?+n) relative references for recursion and subroutines.
181    
182      (?(-n) and (?(+n) relative references as conditions.
183    
184      \k{name} and \g{name} are synonyms for \k<name>.
185    
186      \K to reset the start of the matched string; for example, (foo)\Kbar
187      matches bar preceded by foo, but only sets bar as the matched string.
188    
189      (?| introduces a group where the capturing parentheses in each alternative
190      start from the same number; for example, (?|(abc)|(xyz)) sets capturing
191      parentheses number 1 in both cases.
192    
193      \h, \H, \v, \V match horizontal and vertical whitespace, respectively.
194    
195    
196    Release 7.1 24-Apr-07
197    ---------------------
198    
199    There is only one new feature in this release: a linebreak setting of
200    PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
201    recognizes only CRLF, CR, and LF as linebreaks.
202    
203    A few bugs are fixed (see ChangeLog for details), but the major change is a
204    complete re-implementation of the build system. This now has full Autotools
205    support and so is now "standard" in some sense. It should help with compiling
206    PCRE in a wide variety of environments.
207    
208    NOTE: when building shared libraries for Windows, three dlls are now built,
209    called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
210    included in a single dll.
211    
212    Another important change is that the dftables auxiliary program is no longer
213    compiled and run at "make" time by default. Instead, a default set of character
214    tables (assuming ASCII coding) is used. If you want to use dftables to generate
215    the character tables as previously, add --enable-rebuild-chartables to the
216    "configure" command. You must do this if you are compiling PCRE to run on a
217    system that uses EBCDIC code.
218    
219    There is a discussion about character tables in the README file. The default is
220    not to use dftables so that that there is no problem when cross-compiling.
221    
222    
223    Release 7.0 19-Dec-06
224    ---------------------
225    
226    This release has a new major number because there have been some internal
227    upheavals to facilitate the addition of new optimizations and other facilities,
228    and to make subsequent maintenance and extension easier. Compilation is likely
229    to be a bit slower, but there should be no major effect on runtime performance.
230    Previously compiled patterns are NOT upwards compatible with this release. If
231    you have saved compiled patterns from a previous release, you will have to
232    re-compile them. Important changes that are visible to users are:
233    
234    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
235       some more scripts.
236    
237    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
238       sequence as a newline.
239    
240    3. The \R escape matches a single Unicode newline sequence as a single unit.
241    
242    4. New features that will appear in Perl 5.10 are now in PCRE. These include
243       alternative Perl syntax for named parentheses, and Perl syntax for
244       recursion.
245    
246    5. The C++ wrapper interface has been extended by the addition of a
247       QuoteMeta function and the ability to allow copy construction and
248       assignment.
249    
250    For a complete list of changes, see the ChangeLog file.
251    
252    
253    Release 6.7 04-Jul-06
254    ---------------------
255    
256    The main additions to this release are the ability to use the same name for
257    multiple sets of parentheses, and support for CRLF line endings in both the
258    library and pcregrep (and in pcretest for testing).
259    
260    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
261    significantly reduced for certain subject strings.
262    
263    
264    Release 6.5 01-Feb-06
265    ---------------------
266    
267    Important changes in this release:
268    
269    1. A number of new features have been added to pcregrep.
270    
271    2. The Unicode property tables have been updated to Unicode 4.1.0, and the
272       supported properties have been extended with script names such as "Arabic",
273       and the derived properties "Any" and "L&". This has necessitated a change to
274       the interal format of compiled patterns. Any saved compiled patterns that
275       use \p or \P must be recompiled.
276    
277    3. The specification of recursion in patterns has been changed so that all
278       recursive subpatterns are automatically treated as atomic groups. Thus, for
279       example, (?R) is treated as if it were (?>(?R)). This is necessary because
280       otherwise there are situations where recursion does not work.
281    
282    See the ChangeLog for a complete list of changes, which include a number of bug
283    fixes and tidies.
284    
285    
286    Release 6.0 07-Jun-05
287    ---------------------
288    
289    The release number has been increased to 6.0 because of the addition of several
290    major new pieces of functionality.
291    
292    A new function, pcre_dfa_exec(), which implements pattern matching using a DFA
293    algorithm, has been added. This has a number of advantages for certain cases,
294    though it does run more slowly, and lacks the ability to capture substrings. On
295    the other hand, it does find all matches, not just the first, and it works
296    better for partial matching. The pcrematching man page discusses the
297    differences.
298    
299    The pcretest program has been enhanced so that it can make use of the new
300    pcre_dfa_exec() matching function and the extra features it provides.
301    
302    The distribution now includes a C++ wrapper library. This is built
303    automatically if a C++ compiler is found. The pcrecpp man page discusses this
304    interface.
305    
306    The code itself has been re-organized into many more files, one for each
307    function, so it no longer requires everything to be linked in when static
308    linkage is used. As a consequence, some internal functions have had to have
309    their names exposed. These functions all have names starting with _pcre_. They
310    are undocumented, and are not intended for use by outside callers.
311    
312    The pcregrep program has been enhanced with new functionality such as
313    multiline-matching and options for output more matching context. See the
314    ChangeLog for a complete list of changes to the library and the utility
315    programs.
316    
317    
318    Release 5.0 13-Sep-04
319    ---------------------
320    
321    The licence under which PCRE is released has been changed to the more
322    conventional "BSD" licence.
323    
324    In the code, some bugs have been fixed, and there are also some major changes
325    in this release (which is why I've increased the number to 5.0). Some changes
326    are internal rearrangements, and some provide a number of new facilities. The
327    new features are:
328    
329    1. There's an "automatic callout" feature that inserts callouts before every
330       item in the regex, and there's a new callout field that gives the position
331       in the pattern - useful for debugging and tracing.
332    
333    2. The extra_data structure can now be used to pass in a set of character
334       tables at exec time. This is useful if compiled regex are saved and re-used
335       at a later time when the tables may not be at the same address. If the
336       default internal tables are used, the pointer saved with the compiled
337       pattern is now set to NULL, which means that you don't need to do anything
338       special unless you are using custom tables.
339    
340    3. It is possible, with some restrictions on the content of the regex, to
341       request "partial" matching. A special return code is given if all of the
342       subject string matched part of the regex. This could be useful for testing
343       an input field as it is being typed.
344    
345    4. There is now some optional support for Unicode character properties, which
346       means that the patterns items such as \p{Lu} and \X can now be used. Only
347       the general category properties are supported. If PCRE is compiled with this
348       support, an additional 90K data structure is include, which increases the
349       size of the library dramatically.
350    
351    5. There is support for saving compiled patterns and re-using them later.
352    
353    6. There is support for running regular expressions that were compiled on a
354       different host with the opposite endianness.
355    
356    7. The pcretest program has been extended to accommodate the new features.
357    
358    The main internal rearrangement is that sequences of literal characters are no
359    longer handled as strings. Instead, each character is handled on its own. This
360    makes some UTF-8 handling easier, and makes the support of partial matching
361    possible. Compiled patterns containing long literal strings will be larger as a
362    result of this change; I hope that performance will not be much affected.
363    
364    
365    Release 4.5 01-Dec-03
366    ---------------------
367    
368    Again mainly a bug-fix and tidying release, with only a couple of new features:
369    
370    1. It's possible now to compile PCRE so that it does not use recursive
371    function calls when matching. Instead it gets memory from the heap. This slows
372    things down, but may be necessary on systems with limited stacks.
373    
374    2. UTF-8 string checking has been tightened to reject overlong sequences and to
375    check that a starting offset points to the start of a character. Failure of the
376    latter returns a new error code: PCRE_ERROR_BADUTF8_OFFSET.
377    
378    3. PCRE can now be compiled for systems that use EBCDIC code.
379    
380    
381    Release 4.4 21-Aug-03
382    ---------------------
383    
384    This is mainly a bug-fix and tidying release. The only new feature is that PCRE
385    checks UTF-8 strings for validity by default. There is an option to suppress
386    this, just in case anybody wants that teeny extra bit of performance.
387    
388    
389    Releases 4.1 - 4.3
390    ------------------
391    
392    Sorry, I forgot about updating the NEWS file for these releases. Please take a
393    look at ChangeLog.
394    
395    
396    Release 4.0 17-Feb-03
397    ---------------------
398    
399    There have been a lot of changes for the 4.0 release, adding additional
400    functionality and mending bugs. Below is a list of the highlights of the new
401    functionality. For full details of these features, please consult the
402    documentation. For a complete list of changes, see the ChangeLog file.
403    
404    1. Support for Perl's \Q...\E escapes.
405    
406    2. "Possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's Java
407    package. They provide some syntactic sugar for simple cases of "atomic
408    grouping".
409    
410    3. Support for the \G assertion. It is true when the current matching position
411    is at the start point of the match.
412    
413    4. A new feature that provides some of the functionality that Perl provides
414    with (?{...}). The facility is termed a "callout". The way it is done in PCRE
415    is for the caller to provide an optional function, by setting pcre_callout to
416    its entry point. To get the function called, the regex must include (?C) at
417    appropriate points.
418    
419    5. Support for recursive calls to individual subpatterns. This makes it really
420    easy to get totally confused.
421    
422    6. Support for named subpatterns. The Python syntax (?P<name>...) is used to
423    name a group.
424    
425    7. Several extensions to UTF-8 support; it is now fairly complete. There is an
426    option for pcregrep to make it operate in UTF-8 mode.
427    
428    8. The single man page has been split into a number of separate man pages.
429    These also give rise to individual HTML pages which are put in a separate
430    directory. There is an index.html page that lists them all. Some hyperlinking
431    between the pages has been installed.
432    
433    
434  Release 3.5 15-Aug-01  Release 3.5 15-Aug-01
435  ---------------------  ---------------------
436    

Legend:
Removed from v.53  
changed lines
  Added in v.738

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12