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

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

  ViewVC Help
Powered by ViewVC 1.1.5