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

Diff of /code/trunk/NEWS

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

revision 75 by nigel, Sat Feb 24 21:40:37 2007 UTC revision 159 by ph10, Wed May 2 10:27:18 2007 UTC
# Line 1  Line 1 
1  News about PCRE releases  News about PCRE releases
2  ------------------------  ------------------------
3    
4    
5    Release 7.2 30-Apr-07
6    ---------------------
7    
8    Correction to the notes for 7.1: the note about shared libraries for Windows is
9    wrong. Previously, three libraries were built, but each could function
10    independently. For example, the pcreposix library also included all the
11    functions from the basic pcre library. The change is that the three libraries
12    are no longer independent. They are like the Unix libraries. To use the
13    pcreposix functions, for example, you need to link with both the pcreposix and
14    the basic pcre library.
15    
16    
17    Release 7.1 24-Apr-07
18    ---------------------
19    
20    There is only one new feature in this release: a linebreak setting of
21    PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
22    recognizes only CRLF, CR, and LF as linebreaks.
23    
24    A few bugs are fixed (see ChangeLog for details), but the major change is a
25    complete re-implementation of the build system. This now has full Autotools
26    support and so is now "standard" in some sense. It should help with compiling
27    PCRE in a wide variety of environments.
28    
29    NOTE: when building shared libraries for Windows, three dlls are now built,
30    called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
31    included in a single dll.
32    
33    Another important change is that the dftables auxiliary program is no longer
34    compiled and run at "make" time by default. Instead, a default set of character
35    tables (assuming ASCII coding) is used. If you want to use dftables to generate
36    the character tables as previously, add --enable-rebuild-chartables to the
37    "configure" command. You must do this if you are compiling PCRE to run on a
38    system that uses EBCDIC code.
39    
40    There is a discussion about character tables in the README file. The default is
41    not to use dftables so that that there is no problem when cross-compiling.
42    
43    
44    Release 7.0 19-Dec-06
45    ---------------------
46    
47    This release has a new major number because there have been some internal
48    upheavals to facilitate the addition of new optimizations and other facilities,
49    and to make subsequent maintenance and extension easier. Compilation is likely
50    to be a bit slower, but there should be no major effect on runtime performance.
51    Previously compiled patterns are NOT upwards compatible with this release. If
52    you have saved compiled patterns from a previous release, you will have to
53    re-compile them. Important changes that are visible to users are:
54    
55    1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
56       some more scripts.
57    
58    2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
59       sequence as a newline.
60    
61    3. The \R escape matches a single Unicode newline sequence as a single unit.
62    
63    4. New features that will appear in Perl 5.10 are now in PCRE. These include
64       alternative Perl syntax for named parentheses, and Perl syntax for
65       recursion.
66    
67    5. The C++ wrapper interface has been extended by the addition of a
68       QuoteMeta function and the ability to allow copy construction and
69       assignment.
70    
71    For a complete list of changes, see the ChangeLog file.
72    
73    
74    Release 6.7 04-Jul-06
75    ---------------------
76    
77    The main additions to this release are the ability to use the same name for
78    multiple sets of parentheses, and support for CRLF line endings in both the
79    library and pcregrep (and in pcretest for testing).
80    
81    Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
82    significantly reduced for certain subject strings.
83    
84    
85    Release 6.5 01-Feb-06
86    ---------------------
87    
88    Important changes in this release:
89    
90    1. A number of new features have been added to pcregrep.
91    
92    2. The Unicode property tables have been updated to Unicode 4.1.0, and the
93       supported properties have been extended with script names such as "Arabic",
94       and the derived properties "Any" and "L&". This has necessitated a change to
95       the interal format of compiled patterns. Any saved compiled patterns that
96       use \p or \P must be recompiled.
97    
98    3. The specification of recursion in patterns has been changed so that all
99       recursive subpatterns are automatically treated as atomic groups. Thus, for
100       example, (?R) is treated as if it were (?>(?R)). This is necessary because
101       otherwise there are situations where recursion does not work.
102    
103    See the ChangeLog for a complete list of changes, which include a number of bug
104    fixes and tidies.
105    
106    
107    Release 6.0 07-Jun-05
108    ---------------------
109    
110    The release number has been increased to 6.0 because of the addition of several
111    major new pieces of functionality.
112    
113    A new function, pcre_dfa_exec(), which implements pattern matching using a DFA
114    algorithm, has been added. This has a number of advantages for certain cases,
115    though it does run more slowly, and lacks the ability to capture substrings. On
116    the other hand, it does find all matches, not just the first, and it works
117    better for partial matching. The pcrematching man page discusses the
118    differences.
119    
120    The pcretest program has been enhanced so that it can make use of the new
121    pcre_dfa_exec() matching function and the extra features it provides.
122    
123    The distribution now includes a C++ wrapper library. This is built
124    automatically if a C++ compiler is found. The pcrecpp man page discusses this
125    interface.
126    
127    The code itself has been re-organized into many more files, one for each
128    function, so it no longer requires everything to be linked in when static
129    linkage is used. As a consequence, some internal functions have had to have
130    their names exposed. These functions all have names starting with _pcre_. They
131    are undocumented, and are not intended for use by outside callers.
132    
133    The pcregrep program has been enhanced with new functionality such as
134    multiline-matching and options for output more matching context. See the
135    ChangeLog for a complete list of changes to the library and the utility
136    programs.
137    
138    
139  Release 5.0 13-Sep-04  Release 5.0 13-Sep-04
140  ---------------------  ---------------------
141    

Legend:
Removed from v.75  
changed lines
  Added in v.159

  ViewVC Help
Powered by ViewVC 1.1.5