ViewVC logotype

Diff of /code/trunk/NEWS

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

revision 77 by nigel, Sat Feb 24 21:40:45 2007 UTC revision 220 by ph10, Thu Aug 16 13:29:39 2007 UTC
# Line 1  Line 1 
1  News about PCRE releases  News about PCRE releases
2  ------------------------  ------------------------
5    Release 7.3 16-Aug-07
6    ---------------------
8    Most changes are bug fixes. Some that are not:
10    1. There is some support for Perl 5.10's experimental "backtracking control
11       verbs" such as (*PRUNE).
13    2. UTF-8 checking is now as per RFC 3629 instead of RFC 2279; this is more
14       restrictive in the strings it accepts.
16    3. Checking for potential integer overflow has been made more dynamic, and as a
17       consequence there is no longer a hard limit on the size of a subpattern that
18       has a limited repeat count.
21    Release 7.2 19-Jun-07
22    ---------------------
24    WARNING: saved patterns that were compiled by earlier versions of PCRE must be
25    recompiled for use with 7.2 (necessitated by the addition of \K, \h, \H, \v,
26    and \V).
28    Correction to the notes for 7.1: the note about shared libraries for Windows is
29    wrong. Previously, three libraries were built, but each could function
30    independently. For example, the pcreposix library also included all the
31    functions from the basic pcre library. The change is that the three libraries
32    are no longer independent. They are like the Unix libraries. To use the
33    pcreposix functions, for example, you need to link with both the pcreposix and
34    the basic pcre library.
36    Some more features from Perl 5.10 have been added:
38      (?-n) and (?+n) relative references for recursion and subroutines.
40      (?(-n) and (?(+n) relative references as conditions.
42      \k{name} and \g{name} are synonyms for \k<name>.
44      \K to reset the start of the matched string; for example, (foo)\Kbar
45      matches bar preceded by foo, but only sets bar as the matched string.
47      (?| introduces a group where the capturing parentheses in each alternative
48      start from the same number; for example, (?|(abc)|(xyz)) sets capturing
49      parentheses number 1 in both cases.
51      \h, \H, \v, \V match horizontal and vertical whitespace, respectively.
54    Release 7.1 24-Apr-07
55    ---------------------
57    There is only one new feature in this release: a linebreak setting of
58    PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
59    recognizes only CRLF, CR, and LF as linebreaks.
61    A few bugs are fixed (see ChangeLog for details), but the major change is a
62    complete re-implementation of the build system. This now has full Autotools
63    support and so is now "standard" in some sense. It should help with compiling
64    PCRE in a wide variety of environments.
66    NOTE: when building shared libraries for Windows, three dlls are now built,
67    called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
68    included in a single dll.
70    Another important change is that the dftables auxiliary program is no longer
71    compiled and run at "make" time by default. Instead, a default set of character
72    tables (assuming ASCII coding) is used. If you want to use dftables to generate
73    the character tables as previously, add --enable-rebuild-chartables to the
74    "configure" command. You must do this if you are compiling PCRE to run on a
75    system that uses EBCDIC code.
77    There is a discussion about character tables in the README file. The default is
78    not to use dftables so that that there is no problem when cross-compiling.
81    Release 7.0 19-Dec-06
82    ---------------------
84    This release has a new major number because there have been some internal
85    upheavals to facilitate the addition of new optimizations and other facilities,
86    and to make subsequent maintenance and extension easier. Compilation is likely
87    to be a bit slower, but there should be no major effect on runtime performance.
88    Previously compiled patterns are NOT upwards compatible with this release. If
89    you have saved compiled patterns from a previous release, you will have to
90    re-compile them. Important changes that are visible to users are:
92    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
93       some more scripts.
95    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
96       sequence as a newline.
98    3. The \R escape matches a single Unicode newline sequence as a single unit.
100    4. New features that will appear in Perl 5.10 are now in PCRE. These include
101       alternative Perl syntax for named parentheses, and Perl syntax for
102       recursion.
104    5. The C++ wrapper interface has been extended by the addition of a
105       QuoteMeta function and the ability to allow copy construction and
106       assignment.
108    For a complete list of changes, see the ChangeLog file.
111    Release 6.7 04-Jul-06
112    ---------------------
114    The main additions to this release are the ability to use the same name for
115    multiple sets of parentheses, and support for CRLF line endings in both the
116    library and pcregrep (and in pcretest for testing).
118    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
119    significantly reduced for certain subject strings.
122    Release 6.5 01-Feb-06
123    ---------------------
125    Important changes in this release:
127    1. A number of new features have been added to pcregrep.
129    2. The Unicode property tables have been updated to Unicode 4.1.0, and the
130       supported properties have been extended with script names such as "Arabic",
131       and the derived properties "Any" and "L&". This has necessitated a change to
132       the interal format of compiled patterns. Any saved compiled patterns that
133       use \p or \P must be recompiled.
135    3. The specification of recursion in patterns has been changed so that all
136       recursive subpatterns are automatically treated as atomic groups. Thus, for
137       example, (?R) is treated as if it were (?>(?R)). This is necessary because
138       otherwise there are situations where recursion does not work.
140    See the ChangeLog for a complete list of changes, which include a number of bug
141    fixes and tidies.
144  Release 6.0 07-Jun-05  Release 6.0 07-Jun-05
145  ---------------------  ---------------------

Removed from v.77  
changed lines
  Added in v.220

  ViewVC Help
Powered by ViewVC 1.1.5