1 |
News about PCRE releases
|
2 |
------------------------
|
3 |
|
4 |
Release 4.4 21-Aug-03
|
5 |
---------------------
|
6 |
|
7 |
This is mainly a bug-fix and tidying release. The only new feature is that PCRE
|
8 |
checks UTF-8 strings for validity by default. There is an option to suppress
|
9 |
this, just in case anybody wants that teeny extra bit of performance.
|
10 |
|
11 |
|
12 |
Releases 4.1 - 4.3
|
13 |
------------------
|
14 |
|
15 |
Sorry, I forgot about updating the NEWS file for these releases. Please take a
|
16 |
look at ChangeLog.
|
17 |
|
18 |
|
19 |
Release 4.0 17-Feb-03
|
20 |
---------------------
|
21 |
|
22 |
There have been a lot of changes for the 4.0 release, adding additional
|
23 |
functionality and mending bugs. Below is a list of the highlights of the new
|
24 |
functionality. For full details of these features, please consult the
|
25 |
documentation. For a complete list of changes, see the ChangeLog file.
|
26 |
|
27 |
1. Support for Perl's \Q...\E escapes.
|
28 |
|
29 |
2. "Possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's Java
|
30 |
package. They provide some syntactic sugar for simple cases of "atomic
|
31 |
grouping".
|
32 |
|
33 |
3. Support for the \G assertion. It is true when the current matching position
|
34 |
is at the start point of the match.
|
35 |
|
36 |
4. A new feature that provides some of the functionality that Perl provides
|
37 |
with (?{...}). The facility is termed a "callout". The way it is done in PCRE
|
38 |
is for the caller to provide an optional function, by setting pcre_callout to
|
39 |
its entry point. To get the function called, the regex must include (?C) at
|
40 |
appropriate points.
|
41 |
|
42 |
5. Support for recursive calls to individual subpatterns. This makes it really
|
43 |
easy to get totally confused.
|
44 |
|
45 |
6. Support for named subpatterns. The Python syntax (?P<name>...) is used to
|
46 |
name a group.
|
47 |
|
48 |
7. Several extensions to UTF-8 support; it is now fairly complete. There is an
|
49 |
option for pcregrep to make it operate in UTF-8 mode.
|
50 |
|
51 |
8. The single man page has been split into a number of separate man pages.
|
52 |
These also give rise to individual HTML pages which are put in a separate
|
53 |
directory. There is an index.html page that lists them all. Some hyperlinking
|
54 |
between the pages has been installed.
|
55 |
|
56 |
|
57 |
Release 3.5 15-Aug-01
|
58 |
---------------------
|
59 |
|
60 |
1. The configuring system has been upgraded to use later versions of autoconf
|
61 |
and libtool. By default it builds both a shared and a static library if the OS
|
62 |
supports it. You can use --disable-shared or --disable-static on the configure
|
63 |
command if you want only one of them.
|
64 |
|
65 |
2. The pcretest utility is now installed along with pcregrep because it is
|
66 |
useful for users (to test regexs) and by doing this, it automatically gets
|
67 |
relinked by libtool. The documentation has been turned into a man page, so
|
68 |
there are now .1, .txt, and .html versions in /doc.
|
69 |
|
70 |
3. Upgrades to pcregrep:
|
71 |
(i) Added long-form option names like gnu grep.
|
72 |
(ii) Added --help to list all options with an explanatory phrase.
|
73 |
(iii) Added -r, --recursive to recurse into sub-directories.
|
74 |
(iv) Added -f, --file to read patterns from a file.
|
75 |
|
76 |
4. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure
|
77 |
script, to force use of CR or LF instead of \n in the source. On non-Unix
|
78 |
systems, the value can be set in config.h.
|
79 |
|
80 |
5. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an
|
81 |
absolute limit. Changed the text of the error message to make this clear, and
|
82 |
likewise updated the man page.
|
83 |
|
84 |
6. The limit of 99 on the number of capturing subpatterns has been removed.
|
85 |
The new limit is 65535, which I hope will not be a "real" limit.
|
86 |
|
87 |
|
88 |
Release 3.3 01-Aug-00
|
89 |
---------------------
|
90 |
|
91 |
There is some support for UTF-8 character strings. This is incomplete and
|
92 |
experimental. The documentation describes what is and what is not implemented.
|
93 |
Otherwise, this is just a bug-fixing release.
|
94 |
|
95 |
|
96 |
Release 3.0 01-Feb-00
|
97 |
---------------------
|
98 |
|
99 |
1. A "configure" script is now used to configure PCRE for Unix systems. It
|
100 |
builds a Makefile, a config.h file, and the pcre-config script.
|
101 |
|
102 |
2. PCRE is built as a shared library by default.
|
103 |
|
104 |
3. There is support for POSIX classes such as [:alpha:].
|
105 |
|
106 |
5. There is an experimental recursion feature.
|
107 |
|
108 |
----------------------------------------------------------------------------
|
109 |
IMPORTANT FOR THOSE UPGRADING FROM VERSIONS BEFORE 2.00
|
110 |
|
111 |
Please note that there has been a change in the API such that a larger
|
112 |
ovector is required at matching time, to provide some additional workspace.
|
113 |
The new man page has details. This change was necessary in order to support
|
114 |
some of the new functionality in Perl 5.005.
|
115 |
|
116 |
IMPORTANT FOR THOSE UPGRADING FROM VERSION 2.00
|
117 |
|
118 |
Another (I hope this is the last!) change has been made to the API for the
|
119 |
pcre_compile() function. An additional argument has been added to make it
|
120 |
possible to pass over a pointer to character tables built in the current
|
121 |
locale by pcre_maketables(). To use the default tables, this new arguement
|
122 |
should be passed as NULL.
|
123 |
|
124 |
IMPORTANT FOR THOSE UPGRADING FROM VERSION 2.05
|
125 |
|
126 |
Yet another (and again I hope this really is the last) change has been made
|
127 |
to the API for the pcre_exec() function. An additional argument has been
|
128 |
added to make it possible to start the match other than at the start of the
|
129 |
subject string. This is important if there are lookbehinds. The new man
|
130 |
page has the details, but you just want to convert existing programs, all
|
131 |
you need to do is to stick in a new fifth argument to pcre_exec(), with a
|
132 |
value of zero. For example, change
|
133 |
|
134 |
pcre_exec(pattern, extra, subject, length, options, ovec, ovecsize)
|
135 |
to
|
136 |
pcre_exec(pattern, extra, subject, length, 0, options, ovec, ovecsize)
|
137 |
|
138 |
****
|