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

Diff of /code/trunk/NEWS

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

revision 73 by nigel, Sat Feb 24 21:40:30 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  ------------------------  ------------------------
3    
4    
5    Release 7.3 16-Aug-07
6    ---------------------
7    
8    Most changes are bug fixes. Some that are not:
9    
10    1. There is some support for Perl 5.10's experimental "backtracking control
11       verbs" such as (*PRUNE).
12    
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.
15    
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.
19    
20    
21    Release 7.2 19-Jun-07
22    ---------------------
23    
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).
27    
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.
35    
36    Some more features from Perl 5.10 have been added:
37    
38      (?-n) and (?+n) relative references for recursion and subroutines.
39    
40      (?(-n) and (?(+n) relative references as conditions.
41    
42      \k{name} and \g{name} are synonyms for \k<name>.
43    
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.
46    
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.
50    
51      \h, \H, \v, \V match horizontal and vertical whitespace, respectively.
52    
53    
54    Release 7.1 24-Apr-07
55    ---------------------
56    
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.
60    
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.
65    
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.
69    
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.
76    
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.
79    
80    
81    Release 7.0 19-Dec-06
82    ---------------------
83    
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:
91    
92    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
93       some more scripts.
94    
95    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
96       sequence as a newline.
97    
98    3. The \R escape matches a single Unicode newline sequence as a single unit.
99    
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.
103    
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.
107    
108    For a complete list of changes, see the ChangeLog file.
109    
110    
111    Release 6.7 04-Jul-06
112    ---------------------
113    
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).
117    
118    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
119    significantly reduced for certain subject strings.
120    
121    
122    Release 6.5 01-Feb-06
123    ---------------------
124    
125    Important changes in this release:
126    
127    1. A number of new features have been added to pcregrep.
128    
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.
134    
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.
139    
140    See the ChangeLog for a complete list of changes, which include a number of bug
141    fixes and tidies.
142    
143    
144    Release 6.0 07-Jun-05
145    ---------------------
146    
147    The release number has been increased to 6.0 because of the addition of several
148    major new pieces of functionality.
149    
150    A new function, pcre_dfa_exec(), which implements pattern matching using a DFA
151    algorithm, has been added. This has a number of advantages for certain cases,
152    though it does run more slowly, and lacks the ability to capture substrings. On
153    the other hand, it does find all matches, not just the first, and it works
154    better for partial matching. The pcrematching man page discusses the
155    differences.
156    
157    The pcretest program has been enhanced so that it can make use of the new
158    pcre_dfa_exec() matching function and the extra features it provides.
159    
160    The distribution now includes a C++ wrapper library. This is built
161    automatically if a C++ compiler is found. The pcrecpp man page discusses this
162    interface.
163    
164    The code itself has been re-organized into many more files, one for each
165    function, so it no longer requires everything to be linked in when static
166    linkage is used. As a consequence, some internal functions have had to have
167    their names exposed. These functions all have names starting with _pcre_. They
168    are undocumented, and are not intended for use by outside callers.
169    
170    The pcregrep program has been enhanced with new functionality such as
171    multiline-matching and options for output more matching context. See the
172    ChangeLog for a complete list of changes to the library and the utility
173    programs.
174    
175    
176    Release 5.0 13-Sep-04
177    ---------------------
178    
179    The licence under which PCRE is released has been changed to the more
180    conventional "BSD" licence.
181    
182    In the code, some bugs have been fixed, and there are also some major changes
183    in this release (which is why I've increased the number to 5.0). Some changes
184    are internal rearrangements, and some provide a number of new facilities. The
185    new features are:
186    
187    1. There's an "automatic callout" feature that inserts callouts before every
188       item in the regex, and there's a new callout field that gives the position
189       in the pattern - useful for debugging and tracing.
190    
191    2. The extra_data structure can now be used to pass in a set of character
192       tables at exec time. This is useful if compiled regex are saved and re-used
193       at a later time when the tables may not be at the same address. If the
194       default internal tables are used, the pointer saved with the compiled
195       pattern is now set to NULL, which means that you don't need to do anything
196       special unless you are using custom tables.
197    
198    3. It is possible, with some restrictions on the content of the regex, to
199       request "partial" matching. A special return code is given if all of the
200       subject string matched part of the regex. This could be useful for testing
201       an input field as it is being typed.
202    
203    4. There is now some optional support for Unicode character properties, which
204       means that the patterns items such as \p{Lu} and \X can now be used. Only
205       the general category properties are supported. If PCRE is compiled with this
206       support, an additional 90K data structure is include, which increases the
207       size of the library dramatically.
208    
209    5. There is support for saving compiled patterns and re-using them later.
210    
211    6. There is support for running regular expressions that were compiled on a
212       different host with the opposite endianness.
213    
214    7. The pcretest program has been extended to accommodate the new features.
215    
216    The main internal rearrangement is that sequences of literal characters are no
217    longer handled as strings. Instead, each character is handled on its own. This
218    makes some UTF-8 handling easier, and makes the support of partial matching
219    possible. Compiled patterns containing long literal strings will be larger as a
220    result of this change; I hope that performance will not be much affected.
221    
222    
223  Release 4.5 01-Dec-03  Release 4.5 01-Dec-03
224  ---------------------  ---------------------
225    

Legend:
Removed from v.73  
changed lines
  Added in v.220

  ViewVC Help
Powered by ViewVC 1.1.5