/[pcre]/code/trunk/NEWS
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 319 by ph10, Mon Jan 28 15:27:45 2008 UTC
# Line 1  Line 1 
1  News about PCRE releases  News about PCRE releases
2  ------------------------  ------------------------
3    
4    Release 7.6 28-Jan-08
5    ---------------------
6    
7    The main reason for having this release so soon after 7.5 is because it fixes a
8    potential buffer overflow problem in pcre_compile() when run in UTF-8 mode. In
9    addition, the CMake configuration files have been brought up to date.
10    
11    
12    Release 7.5 10-Jan-08
13    ---------------------
14    
15    This is mainly a bug-fix release. However the ability to link pcregrep with
16    libz or libbz2 and the ability to link pcretest with libreadline have been
17    added. Also the --line-offsets and --file-offsets options were added to
18    pcregrep.
19    
20    
21    Release 7.4 21-Sep-07
22    ---------------------
23    
24    The only change of specification is the addition of options to control whether
25    \R matches any Unicode line ending (the default) or just CR, LF, and CRLF.
26    Otherwise, the changes are bug fixes and a refactoring to reduce the number of
27    relocations needed in a shared library. There have also been some documentation
28    updates, in particular, some more information about using CMake to build PCRE
29    has been added to the NON-UNIX-USE file.
30    
31    
32    Release 7.3 28-Aug-07
33    ---------------------
34    
35    Most changes are bug fixes. Some that are not:
36    
37    1. There is some support for Perl 5.10's experimental "backtracking control
38       verbs" such as (*PRUNE).
39    
40    2. UTF-8 checking is now as per RFC 3629 instead of RFC 2279; this is more
41       restrictive in the strings it accepts.
42    
43    3. Checking for potential integer overflow has been made more dynamic, and as a
44       consequence there is no longer a hard limit on the size of a subpattern that
45       has a limited repeat count.
46    
47    4. When CRLF is a valid line-ending sequence, pcre_exec() and pcre_dfa_exec()
48       no longer advance by two characters instead of one when an unanchored match
49       fails at CRLF if there are explicit CR or LF matches within the pattern.
50       This gets rid of some anomalous effects that previously occurred.
51    
52    5. Some PCRE-specific settings for varying the newline options at the start of
53       a pattern have been added.
54    
55    
56    Release 7.2 19-Jun-07
57    ---------------------
58    
59    WARNING: saved patterns that were compiled by earlier versions of PCRE must be
60    recompiled for use with 7.2 (necessitated by the addition of \K, \h, \H, \v,
61    and \V).
62    
63    Correction to the notes for 7.1: the note about shared libraries for Windows is
64    wrong. Previously, three libraries were built, but each could function
65    independently. For example, the pcreposix library also included all the
66    functions from the basic pcre library. The change is that the three libraries
67    are no longer independent. They are like the Unix libraries. To use the
68    pcreposix functions, for example, you need to link with both the pcreposix and
69    the basic pcre library.
70    
71    Some more features from Perl 5.10 have been added:
72    
73      (?-n) and (?+n) relative references for recursion and subroutines.
74    
75      (?(-n) and (?(+n) relative references as conditions.
76    
77      \k{name} and \g{name} are synonyms for \k<name>.
78    
79      \K to reset the start of the matched string; for example, (foo)\Kbar
80      matches bar preceded by foo, but only sets bar as the matched string.
81    
82      (?| introduces a group where the capturing parentheses in each alternative
83      start from the same number; for example, (?|(abc)|(xyz)) sets capturing
84      parentheses number 1 in both cases.
85    
86      \h, \H, \v, \V match horizontal and vertical whitespace, respectively.
87    
88    
89    Release 7.1 24-Apr-07
90    ---------------------
91    
92    There is only one new feature in this release: a linebreak setting of
93    PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
94    recognizes only CRLF, CR, and LF as linebreaks.
95    
96    A few bugs are fixed (see ChangeLog for details), but the major change is a
97    complete re-implementation of the build system. This now has full Autotools
98    support and so is now "standard" in some sense. It should help with compiling
99    PCRE in a wide variety of environments.
100    
101    NOTE: when building shared libraries for Windows, three dlls are now built,
102    called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
103    included in a single dll.
104    
105    Another important change is that the dftables auxiliary program is no longer
106    compiled and run at "make" time by default. Instead, a default set of character
107    tables (assuming ASCII coding) is used. If you want to use dftables to generate
108    the character tables as previously, add --enable-rebuild-chartables to the
109    "configure" command. You must do this if you are compiling PCRE to run on a
110    system that uses EBCDIC code.
111    
112    There is a discussion about character tables in the README file. The default is
113    not to use dftables so that that there is no problem when cross-compiling.
114    
115    
116    Release 7.0 19-Dec-06
117    ---------------------
118    
119    This release has a new major number because there have been some internal
120    upheavals to facilitate the addition of new optimizations and other facilities,
121    and to make subsequent maintenance and extension easier. Compilation is likely
122    to be a bit slower, but there should be no major effect on runtime performance.
123    Previously compiled patterns are NOT upwards compatible with this release. If
124    you have saved compiled patterns from a previous release, you will have to
125    re-compile them. Important changes that are visible to users are:
126    
127    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
128       some more scripts.
129    
130    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
131       sequence as a newline.
132    
133    3. The \R escape matches a single Unicode newline sequence as a single unit.
134    
135    4. New features that will appear in Perl 5.10 are now in PCRE. These include
136       alternative Perl syntax for named parentheses, and Perl syntax for
137       recursion.
138    
139    5. The C++ wrapper interface has been extended by the addition of a
140       QuoteMeta function and the ability to allow copy construction and
141       assignment.
142    
143    For a complete list of changes, see the ChangeLog file.
144    
145    
146    Release 6.7 04-Jul-06
147    ---------------------
148    
149    The main additions to this release are the ability to use the same name for
150    multiple sets of parentheses, and support for CRLF line endings in both the
151    library and pcregrep (and in pcretest for testing).
152    
153    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
154    significantly reduced for certain subject strings.
155    
156    
157    Release 6.5 01-Feb-06
158    ---------------------
159    
160    Important changes in this release:
161    
162    1. A number of new features have been added to pcregrep.
163    
164    2. The Unicode property tables have been updated to Unicode 4.1.0, and the
165       supported properties have been extended with script names such as "Arabic",
166       and the derived properties "Any" and "L&". This has necessitated a change to
167       the interal format of compiled patterns. Any saved compiled patterns that
168       use \p or \P must be recompiled.
169    
170    3. The specification of recursion in patterns has been changed so that all
171       recursive subpatterns are automatically treated as atomic groups. Thus, for
172       example, (?R) is treated as if it were (?>(?R)). This is necessary because
173       otherwise there are situations where recursion does not work.
174    
175    See the ChangeLog for a complete list of changes, which include a number of bug
176    fixes and tidies.
177    
178    
179  Release 6.0 07-Jun-05  Release 6.0 07-Jun-05
180  ---------------------  ---------------------
181    

Legend:
Removed from v.77  
changed lines
  Added in v.319

  ViewVC Help
Powered by ViewVC 1.1.5