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 155 by ph10, Tue Apr 24 13:36:11 2007 UTC
# Line 1  Line 1 
1  News about PCRE releases  News about PCRE releases
2  ------------------------  ------------------------
5    Release 7.1 24-Apr-07
6    ---------------------
8    There is only one new feature in this release: a linebreak setting of
9    PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
10    recognizes only CRLF, CR, and LF as linebreaks.
12    A few bugs are fixed (see ChangeLog for details), but the major change is a
13    complete re-implementation of the build system. This now has full Autotools
14    support and so is now "standard" in some sense. It should help with compiling
15    PCRE in a wide variety of environments.
17    NOTE: when building shared libraries for Windows, three dlls are now built,
18    called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
19    included in a single dll.
21    Another important change is that the dftables auxiliary program is no longer
22    compiled and run at "make" time by default. Instead, a default set of character
23    tables (assuming ASCII coding) is used. If you want to use dftables to generate
24    the character tables as previously, add --enable-rebuild-chartables to the
25    "configure" command. You must do this if you are compiling PCRE to run on a
26    system that uses EBCDIC code.
28    There is a discussion about character tables in the README file. The default is
29    not to use dftables so that that there is no problem when cross-compiling.
32    Release 7.0 19-Dec-06
33    ---------------------
35    This release has a new major number because there have been some internal
36    upheavals to facilitate the addition of new optimizations and other facilities,
37    and to make subsequent maintenance and extension easier. Compilation is likely
38    to be a bit slower, but there should be no major effect on runtime performance.
39    Previously compiled patterns are NOT upwards compatible with this release. If
40    you have saved compiled patterns from a previous release, you will have to
41    re-compile them. Important changes that are visible to users are:
43    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
44       some more scripts.
46    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
47       sequence as a newline.
49    3. The \R escape matches a single Unicode newline sequence as a single unit.
51    4. New features that will appear in Perl 5.10 are now in PCRE. These include
52       alternative Perl syntax for named parentheses, and Perl syntax for
53       recursion.
55    5. The C++ wrapper interface has been extended by the addition of a
56       QuoteMeta function and the ability to allow copy construction and
57       assignment.
59    For a complete list of changes, see the ChangeLog file.
62    Release 6.7 04-Jul-06
63    ---------------------
65    The main additions to this release are the ability to use the same name for
66    multiple sets of parentheses, and support for CRLF line endings in both the
67    library and pcregrep (and in pcretest for testing).
69    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
70    significantly reduced for certain subject strings.
73    Release 6.5 01-Feb-06
74    ---------------------
76    Important changes in this release:
78    1. A number of new features have been added to pcregrep.
80    2. The Unicode property tables have been updated to Unicode 4.1.0, and the
81       supported properties have been extended with script names such as "Arabic",
82       and the derived properties "Any" and "L&". This has necessitated a change to
83       the interal format of compiled patterns. Any saved compiled patterns that
84       use \p or \P must be recompiled.
86    3. The specification of recursion in patterns has been changed so that all
87       recursive subpatterns are automatically treated as atomic groups. Thus, for
88       example, (?R) is treated as if it were (?>(?R)). This is necessary because
89       otherwise there are situations where recursion does not work.
91    See the ChangeLog for a complete list of changes, which include a number of bug
92    fixes and tidies.
95    Release 6.0 07-Jun-05
96    ---------------------
98    The release number has been increased to 6.0 because of the addition of several
99    major new pieces of functionality.
101    A new function, pcre_dfa_exec(), which implements pattern matching using a DFA
102    algorithm, has been added. This has a number of advantages for certain cases,
103    though it does run more slowly, and lacks the ability to capture substrings. On
104    the other hand, it does find all matches, not just the first, and it works
105    better for partial matching. The pcrematching man page discusses the
106    differences.
108    The pcretest program has been enhanced so that it can make use of the new
109    pcre_dfa_exec() matching function and the extra features it provides.
111    The distribution now includes a C++ wrapper library. This is built
112    automatically if a C++ compiler is found. The pcrecpp man page discusses this
113    interface.
115    The code itself has been re-organized into many more files, one for each
116    function, so it no longer requires everything to be linked in when static
117    linkage is used. As a consequence, some internal functions have had to have
118    their names exposed. These functions all have names starting with _pcre_. They
119    are undocumented, and are not intended for use by outside callers.
121    The pcregrep program has been enhanced with new functionality such as
122    multiline-matching and options for output more matching context. See the
123    ChangeLog for a complete list of changes to the library and the utility
124    programs.
127    Release 5.0 13-Sep-04
128    ---------------------
130    The licence under which PCRE is released has been changed to the more
131    conventional "BSD" licence.
133    In the code, some bugs have been fixed, and there are also some major changes
134    in this release (which is why I've increased the number to 5.0). Some changes
135    are internal rearrangements, and some provide a number of new facilities. The
136    new features are:
138    1. There's an "automatic callout" feature that inserts callouts before every
139       item in the regex, and there's a new callout field that gives the position
140       in the pattern - useful for debugging and tracing.
142    2. The extra_data structure can now be used to pass in a set of character
143       tables at exec time. This is useful if compiled regex are saved and re-used
144       at a later time when the tables may not be at the same address. If the
145       default internal tables are used, the pointer saved with the compiled
146       pattern is now set to NULL, which means that you don't need to do anything
147       special unless you are using custom tables.
149    3. It is possible, with some restrictions on the content of the regex, to
150       request "partial" matching. A special return code is given if all of the
151       subject string matched part of the regex. This could be useful for testing
152       an input field as it is being typed.
154    4. There is now some optional support for Unicode character properties, which
155       means that the patterns items such as \p{Lu} and \X can now be used. Only
156       the general category properties are supported. If PCRE is compiled with this
157       support, an additional 90K data structure is include, which increases the
158       size of the library dramatically.
160    5. There is support for saving compiled patterns and re-using them later.
162    6. There is support for running regular expressions that were compiled on a
163       different host with the opposite endianness.
165    7. The pcretest program has been extended to accommodate the new features.
167    The main internal rearrangement is that sequences of literal characters are no
168    longer handled as strings. Instead, each character is handled on its own. This
169    makes some UTF-8 handling easier, and makes the support of partial matching
170    possible. Compiled patterns containing long literal strings will be larger as a
171    result of this change; I hope that performance will not be much affected.
174  Release 4.5 01-Dec-03  Release 4.5 01-Dec-03
175  ---------------------  ---------------------

Removed from v.73  
changed lines
  Added in v.155

  ViewVC Help
Powered by ViewVC 1.1.5