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

Contents of /code/trunk/NEWS

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1033 - (show annotations)
Mon Sep 10 11:02:48 2012 UTC (7 years ago) by ph10
File size: 23107 byte(s)
General spring-clean of EBCDIC-related issues in the code, which had decayed 
over time. Also the documentation. Added one test that can be run in an ASCII
world to do a little testing of EBCDIC-related things. 
1 News about PCRE releases
2 ------------------------
3
4 Release 8.32 xx-xxxx-2012
5 -------------------------
6
7 . A number of issues in pcregrep have been fixed, making it more compatible
8 with GNU grep. In particular, --exclude and --include (and variants) apply
9 to all files now, not just those obtained from scanning a directory
10 recursively. In Windows environments, the default action for directories is
11 now "skip" instead of "read" (which provokes an error).
12
13 . \X now matches a Unicode extended grapheme cluster.
14
15 . The EBCDIC support, which had decayed, has had a spring clean.
16
17
18 Release 8.31 06-July-2012
19 -------------------------
20
21 This is mainly a bug-fixing release, with a small number of developments:
22
23 . The JIT compiler now supports partial matching and the (*MARK) and
24 (*COMMIT) verbs.
25
26 . PCRE_INFO_MAXLOOKBEHIND can be used to find the longest lookbehind in a
27 pattern.
28
29 . There should be a performance improvement when using the heap instead of the
30 stack for recursion.
31
32 . pcregrep can now be linked with libedit as an alternative to libreadline.
33
34 . pcregrep now has a --file-list option where the list of files to scan is
35 given as a file.
36
37 . pcregrep now recognizes binary files and there are related options.
38
39 . The Unicode tables have been updated to 6.1.0.
40
41 As always, the full list of changes is in the ChangeLog file.
42
43
44 Release 8.30 04-February-2012
45 -----------------------------
46
47 Release 8.30 introduces a major new feature: support for 16-bit character
48 strings, compiled as a separate library. There are a few changes to the
49 8-bit library, in addition to some bug fixes.
50
51 . The pcre_info() function, which has been obsolete for over 10 years, has
52 been removed.
53
54 . When a compiled pattern was saved to a file and later reloaded on a host
55 with different endianness, PCRE used automatically to swap the bytes in some
56 of the data fields. With the advent of the 16-bit library, where more of this
57 swapping is needed, it is no longer done automatically. Instead, the bad
58 endianness is detected and a specific error is given. The user can then call
59 a new function called pcre_pattern_to_host_byte_order() (or an equivalent
60 16-bit function) to do the swap.
61
62 . In UTF-8 mode, the values 0xd800 to 0xdfff are not legal Unicode
63 code points and are now faulted. (They are the so-called "surrogates"
64 that are reserved for coding high values in UTF-16.)
65
66
67 Release 8.21 12-Dec-2011
68 ------------------------
69
70 This is almost entirely a bug-fix release. The only new feature is the ability
71 to obtain the size of the memory used by the JIT compiler.
72
73
74 Release 8.20 21-Oct-2011
75 ------------------------
76
77 The main change in this release is the inclusion of Zoltan Herczeg's
78 just-in-time compiler support, which can be accessed by building PCRE with
79 --enable-jit. Large performance benefits can be had in many situations. 8.20
80 also fixes an unfortunate bug that was introduced in 8.13 as well as tidying up
81 a number of infelicities and differences from Perl.
82
83
84 Release 8.13 16-Aug-2011
85 ------------------------
86
87 This is mainly a bug-fix release. There has been a lot of internal refactoring.
88 The Unicode tables have been updated. The only new feature in the library is
89 the passing of *MARK information to callouts. Some additions have been made to
90 pcretest to make testing easier and more comprehensive. There is a new option
91 for pcregrep to adjust its internal buffer size.
92
93
94 Release 8.12 15-Jan-2011
95 ------------------------
96
97 This release fixes some bugs in pcregrep, one of which caused the tests to fail
98 on 64-bit big-endian systems. There are no changes to the code of the library.
99
100
101 Release 8.11 10-Dec-2010
102 ------------------------
103
104 A number of bugs in the library and in pcregrep have been fixed. As always, see
105 ChangeLog for details. The following are the non-bug-fix changes:
106
107 . Added --match-limit and --recursion-limit to pcregrep.
108
109 . Added an optional parentheses number to the -o and --only-matching options
110 of pcregrep.
111
112 . Changed the way PCRE_PARTIAL_HARD affects the matching of $, \z, \Z, \b, and
113 \B.
114
115 . Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
116 bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
117
118 . Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
119 START_OPTIMIZE option, which is now allowed at compile time
120
121
122 Release 8.10 25-Jun-2010
123 ------------------------
124
125 There are two major additions: support for (*MARK) and friends, and the option
126 PCRE_UCP, which changes the behaviour of \b, \d, \s, and \w (and their
127 opposites) so that they make use of Unicode properties. There are also a number
128 of lesser new features, and several bugs have been fixed. A new option,
129 --line-buffered, has been added to pcregrep, for use when it is connected to
130 pipes.
131
132
133 Release 8.02 19-Mar-2010
134 ------------------------
135
136 Another bug-fix release.
137
138
139 Release 8.01 19-Jan-2010
140 ------------------------
141
142 This is a bug-fix release. Several bugs in the code itself and some bugs and
143 infelicities in the build system have been fixed.
144
145
146 Release 8.00 19-Oct-09
147 ----------------------
148
149 Bugs have been fixed in the library and in pcregrep. There are also some
150 enhancements. Restrictions on patterns used for partial matching have been
151 removed, extra information is given for partial matches, the partial matching
152 process has been improved, and an option to make a partial match override a
153 full match is available. The "study" process has been enhanced by finding a
154 lower bound matching length. Groups with duplicate numbers may now have
155 duplicated names without the use of PCRE_DUPNAMES. However, they may not have
156 different names. The documentation has been revised to reflect these changes.
157 The version number has been expanded to 3 digits as it is clear that the rate
158 of change is not slowing down.
159
160
161 Release 7.9 11-Apr-09
162 ---------------------
163
164 Mostly bugfixes and tidies with just a couple of minor functional additions.
165
166
167 Release 7.8 05-Sep-08
168 ---------------------
169
170 More bug fixes, plus a performance improvement in Unicode character property
171 lookup.
172
173
174 Release 7.7 07-May-08
175 ---------------------
176
177 This is once again mainly a bug-fix release, but there are a couple of new
178 features.
179
180
181 Release 7.6 28-Jan-08
182 ---------------------
183
184 The main reason for having this release so soon after 7.5 is because it fixes a
185 potential buffer overflow problem in pcre_compile() when run in UTF-8 mode. In
186 addition, the CMake configuration files have been brought up to date.
187
188
189 Release 7.5 10-Jan-08
190 ---------------------
191
192 This is mainly a bug-fix release. However the ability to link pcregrep with
193 libz or libbz2 and the ability to link pcretest with libreadline have been
194 added. Also the --line-offsets and --file-offsets options were added to
195 pcregrep.
196
197
198 Release 7.4 21-Sep-07
199 ---------------------
200
201 The only change of specification is the addition of options to control whether
202 \R matches any Unicode line ending (the default) or just CR, LF, and CRLF.
203 Otherwise, the changes are bug fixes and a refactoring to reduce the number of
204 relocations needed in a shared library. There have also been some documentation
205 updates, in particular, some more information about using CMake to build PCRE
206 has been added to the NON-UNIX-USE file.
207
208
209 Release 7.3 28-Aug-07
210 ---------------------
211
212 Most changes are bug fixes. Some that are not:
213
214 1. There is some support for Perl 5.10's experimental "backtracking control
215 verbs" such as (*PRUNE).
216
217 2. UTF-8 checking is now as per RFC 3629 instead of RFC 2279; this is more
218 restrictive in the strings it accepts.
219
220 3. Checking for potential integer overflow has been made more dynamic, and as a
221 consequence there is no longer a hard limit on the size of a subpattern that
222 has a limited repeat count.
223
224 4. When CRLF is a valid line-ending sequence, pcre_exec() and pcre_dfa_exec()
225 no longer advance by two characters instead of one when an unanchored match
226 fails at CRLF if there are explicit CR or LF matches within the pattern.
227 This gets rid of some anomalous effects that previously occurred.
228
229 5. Some PCRE-specific settings for varying the newline options at the start of
230 a pattern have been added.
231
232
233 Release 7.2 19-Jun-07
234 ---------------------
235
236 WARNING: saved patterns that were compiled by earlier versions of PCRE must be
237 recompiled for use with 7.2 (necessitated by the addition of \K, \h, \H, \v,
238 and \V).
239
240 Correction to the notes for 7.1: the note about shared libraries for Windows is
241 wrong. Previously, three libraries were built, but each could function
242 independently. For example, the pcreposix library also included all the
243 functions from the basic pcre library. The change is that the three libraries
244 are no longer independent. They are like the Unix libraries. To use the
245 pcreposix functions, for example, you need to link with both the pcreposix and
246 the basic pcre library.
247
248 Some more features from Perl 5.10 have been added:
249
250 (?-n) and (?+n) relative references for recursion and subroutines.
251
252 (?(-n) and (?(+n) relative references as conditions.
253
254 \k{name} and \g{name} are synonyms for \k<name>.
255
256 \K to reset the start of the matched string; for example, (foo)\Kbar
257 matches bar preceded by foo, but only sets bar as the matched string.
258
259 (?| introduces a group where the capturing parentheses in each alternative
260 start from the same number; for example, (?|(abc)|(xyz)) sets capturing
261 parentheses number 1 in both cases.
262
263 \h, \H, \v, \V match horizontal and vertical whitespace, respectively.
264
265
266 Release 7.1 24-Apr-07
267 ---------------------
268
269 There is only one new feature in this release: a linebreak setting of
270 PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which
271 recognizes only CRLF, CR, and LF as linebreaks.
272
273 A few bugs are fixed (see ChangeLog for details), but the major change is a
274 complete re-implementation of the build system. This now has full Autotools
275 support and so is now "standard" in some sense. It should help with compiling
276 PCRE in a wide variety of environments.
277
278 NOTE: when building shared libraries for Windows, three dlls are now built,
279 called libpcre, libpcreposix, and libpcrecpp. Previously, everything was
280 included in a single dll.
281
282 Another important change is that the dftables auxiliary program is no longer
283 compiled and run at "make" time by default. Instead, a default set of character
284 tables (assuming ASCII coding) is used. If you want to use dftables to generate
285 the character tables as previously, add --enable-rebuild-chartables to the
286 "configure" command. You must do this if you are compiling PCRE to run on a
287 system that uses EBCDIC code.
288
289 There is a discussion about character tables in the README file. The default is
290 not to use dftables so that that there is no problem when cross-compiling.
291
292
293 Release 7.0 19-Dec-06
294 ---------------------
295
296 This release has a new major number because there have been some internal
297 upheavals to facilitate the addition of new optimizations and other facilities,
298 and to make subsequent maintenance and extension easier. Compilation is likely
299 to be a bit slower, but there should be no major effect on runtime performance.
300 Previously compiled patterns are NOT upwards compatible with this release. If
301 you have saved compiled patterns from a previous release, you will have to
302 re-compile them. Important changes that are visible to users are:
303
304 1. The Unicode property tables have been updated to Unicode 5.0.0, which adds
305 some more scripts.
306
307 2. The option PCRE_NEWLINE_ANY causes PCRE to recognize any Unicode newline
308 sequence as a newline.
309
310 3. The \R escape matches a single Unicode newline sequence as a single unit.
311
312 4. New features that will appear in Perl 5.10 are now in PCRE. These include
313 alternative Perl syntax for named parentheses, and Perl syntax for
314 recursion.
315
316 5. The C++ wrapper interface has been extended by the addition of a
317 QuoteMeta function and the ability to allow copy construction and
318 assignment.
319
320 For a complete list of changes, see the ChangeLog file.
321
322
323 Release 6.7 04-Jul-06
324 ---------------------
325
326 The main additions to this release are the ability to use the same name for
327 multiple sets of parentheses, and support for CRLF line endings in both the
328 library and pcregrep (and in pcretest for testing).
329
330 Thanks to Ian Taylor, the stack usage for many kinds of pattern has been
331 significantly reduced for certain subject strings.
332
333
334 Release 6.5 01-Feb-06
335 ---------------------
336
337 Important changes in this release:
338
339 1. A number of new features have been added to pcregrep.
340
341 2. The Unicode property tables have been updated to Unicode 4.1.0, and the
342 supported properties have been extended with script names such as "Arabic",
343 and the derived properties "Any" and "L&". This has necessitated a change to
344 the interal format of compiled patterns. Any saved compiled patterns that
345 use \p or \P must be recompiled.
346
347 3. The specification of recursion in patterns has been changed so that all
348 recursive subpatterns are automatically treated as atomic groups. Thus, for
349 example, (?R) is treated as if it were (?>(?R)). This is necessary because
350 otherwise there are situations where recursion does not work.
351
352 See the ChangeLog for a complete list of changes, which include a number of bug
353 fixes and tidies.
354
355
356 Release 6.0 07-Jun-05
357 ---------------------
358
359 The release number has been increased to 6.0 because of the addition of several
360 major new pieces of functionality.
361
362 A new function, pcre_dfa_exec(), which implements pattern matching using a DFA
363 algorithm, has been added. This has a number of advantages for certain cases,
364 though it does run more slowly, and lacks the ability to capture substrings. On
365 the other hand, it does find all matches, not just the first, and it works
366 better for partial matching. The pcrematching man page discusses the
367 differences.
368
369 The pcretest program has been enhanced so that it can make use of the new
370 pcre_dfa_exec() matching function and the extra features it provides.
371
372 The distribution now includes a C++ wrapper library. This is built
373 automatically if a C++ compiler is found. The pcrecpp man page discusses this
374 interface.
375
376 The code itself has been re-organized into many more files, one for each
377 function, so it no longer requires everything to be linked in when static
378 linkage is used. As a consequence, some internal functions have had to have
379 their names exposed. These functions all have names starting with _pcre_. They
380 are undocumented, and are not intended for use by outside callers.
381
382 The pcregrep program has been enhanced with new functionality such as
383 multiline-matching and options for output more matching context. See the
384 ChangeLog for a complete list of changes to the library and the utility
385 programs.
386
387
388 Release 5.0 13-Sep-04
389 ---------------------
390
391 The licence under which PCRE is released has been changed to the more
392 conventional "BSD" licence.
393
394 In the code, some bugs have been fixed, and there are also some major changes
395 in this release (which is why I've increased the number to 5.0). Some changes
396 are internal rearrangements, and some provide a number of new facilities. The
397 new features are:
398
399 1. There's an "automatic callout" feature that inserts callouts before every
400 item in the regex, and there's a new callout field that gives the position
401 in the pattern - useful for debugging and tracing.
402
403 2. The extra_data structure can now be used to pass in a set of character
404 tables at exec time. This is useful if compiled regex are saved and re-used
405 at a later time when the tables may not be at the same address. If the
406 default internal tables are used, the pointer saved with the compiled
407 pattern is now set to NULL, which means that you don't need to do anything
408 special unless you are using custom tables.
409
410 3. It is possible, with some restrictions on the content of the regex, to
411 request "partial" matching. A special return code is given if all of the
412 subject string matched part of the regex. This could be useful for testing
413 an input field as it is being typed.
414
415 4. There is now some optional support for Unicode character properties, which
416 means that the patterns items such as \p{Lu} and \X can now be used. Only
417 the general category properties are supported. If PCRE is compiled with this
418 support, an additional 90K data structure is include, which increases the
419 size of the library dramatically.
420
421 5. There is support for saving compiled patterns and re-using them later.
422
423 6. There is support for running regular expressions that were compiled on a
424 different host with the opposite endianness.
425
426 7. The pcretest program has been extended to accommodate the new features.
427
428 The main internal rearrangement is that sequences of literal characters are no
429 longer handled as strings. Instead, each character is handled on its own. This
430 makes some UTF-8 handling easier, and makes the support of partial matching
431 possible. Compiled patterns containing long literal strings will be larger as a
432 result of this change; I hope that performance will not be much affected.
433
434
435 Release 4.5 01-Dec-03
436 ---------------------
437
438 Again mainly a bug-fix and tidying release, with only a couple of new features:
439
440 1. It's possible now to compile PCRE so that it does not use recursive
441 function calls when matching. Instead it gets memory from the heap. This slows
442 things down, but may be necessary on systems with limited stacks.
443
444 2. UTF-8 string checking has been tightened to reject overlong sequences and to
445 check that a starting offset points to the start of a character. Failure of the
446 latter returns a new error code: PCRE_ERROR_BADUTF8_OFFSET.
447
448 3. PCRE can now be compiled for systems that use EBCDIC code.
449
450
451 Release 4.4 21-Aug-03
452 ---------------------
453
454 This is mainly a bug-fix and tidying release. The only new feature is that PCRE
455 checks UTF-8 strings for validity by default. There is an option to suppress
456 this, just in case anybody wants that teeny extra bit of performance.
457
458
459 Releases 4.1 - 4.3
460 ------------------
461
462 Sorry, I forgot about updating the NEWS file for these releases. Please take a
463 look at ChangeLog.
464
465
466 Release 4.0 17-Feb-03
467 ---------------------
468
469 There have been a lot of changes for the 4.0 release, adding additional
470 functionality and mending bugs. Below is a list of the highlights of the new
471 functionality. For full details of these features, please consult the
472 documentation. For a complete list of changes, see the ChangeLog file.
473
474 1. Support for Perl's \Q...\E escapes.
475
476 2. "Possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's Java
477 package. They provide some syntactic sugar for simple cases of "atomic
478 grouping".
479
480 3. Support for the \G assertion. It is true when the current matching position
481 is at the start point of the match.
482
483 4. A new feature that provides some of the functionality that Perl provides
484 with (?{...}). The facility is termed a "callout". The way it is done in PCRE
485 is for the caller to provide an optional function, by setting pcre_callout to
486 its entry point. To get the function called, the regex must include (?C) at
487 appropriate points.
488
489 5. Support for recursive calls to individual subpatterns. This makes it really
490 easy to get totally confused.
491
492 6. Support for named subpatterns. The Python syntax (?P<name>...) is used to
493 name a group.
494
495 7. Several extensions to UTF-8 support; it is now fairly complete. There is an
496 option for pcregrep to make it operate in UTF-8 mode.
497
498 8. The single man page has been split into a number of separate man pages.
499 These also give rise to individual HTML pages which are put in a separate
500 directory. There is an index.html page that lists them all. Some hyperlinking
501 between the pages has been installed.
502
503
504 Release 3.5 15-Aug-01
505 ---------------------
506
507 1. The configuring system has been upgraded to use later versions of autoconf
508 and libtool. By default it builds both a shared and a static library if the OS
509 supports it. You can use --disable-shared or --disable-static on the configure
510 command if you want only one of them.
511
512 2. The pcretest utility is now installed along with pcregrep because it is
513 useful for users (to test regexs) and by doing this, it automatically gets
514 relinked by libtool. The documentation has been turned into a man page, so
515 there are now .1, .txt, and .html versions in /doc.
516
517 3. Upgrades to pcregrep:
518 (i) Added long-form option names like gnu grep.
519 (ii) Added --help to list all options with an explanatory phrase.
520 (iii) Added -r, --recursive to recurse into sub-directories.
521 (iv) Added -f, --file to read patterns from a file.
522
523 4. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure
524 script, to force use of CR or LF instead of \n in the source. On non-Unix
525 systems, the value can be set in config.h.
526
527 5. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an
528 absolute limit. Changed the text of the error message to make this clear, and
529 likewise updated the man page.
530
531 6. The limit of 99 on the number of capturing subpatterns has been removed.
532 The new limit is 65535, which I hope will not be a "real" limit.
533
534
535 Release 3.3 01-Aug-00
536 ---------------------
537
538 There is some support for UTF-8 character strings. This is incomplete and
539 experimental. The documentation describes what is and what is not implemented.
540 Otherwise, this is just a bug-fixing release.
541
542
543 Release 3.0 01-Feb-00
544 ---------------------
545
546 1. A "configure" script is now used to configure PCRE for Unix systems. It
547 builds a Makefile, a config.h file, and the pcre-config script.
548
549 2. PCRE is built as a shared library by default.
550
551 3. There is support for POSIX classes such as [:alpha:].
552
553 5. There is an experimental recursion feature.
554
555 ----------------------------------------------------------------------------
556 IMPORTANT FOR THOSE UPGRADING FROM VERSIONS BEFORE 2.00
557
558 Please note that there has been a change in the API such that a larger
559 ovector is required at matching time, to provide some additional workspace.
560 The new man page has details. This change was necessary in order to support
561 some of the new functionality in Perl 5.005.
562
563 IMPORTANT FOR THOSE UPGRADING FROM VERSION 2.00
564
565 Another (I hope this is the last!) change has been made to the API for the
566 pcre_compile() function. An additional argument has been added to make it
567 possible to pass over a pointer to character tables built in the current
568 locale by pcre_maketables(). To use the default tables, this new arguement
569 should be passed as NULL.
570
571 IMPORTANT FOR THOSE UPGRADING FROM VERSION 2.05
572
573 Yet another (and again I hope this really is the last) change has been made
574 to the API for the pcre_exec() function. An additional argument has been
575 added to make it possible to start the match other than at the start of the
576 subject string. This is important if there are lookbehinds. The new man
577 page has the details, but you just want to convert existing programs, all
578 you need to do is to stick in a new fifth argument to pcre_exec(), with a
579 value of zero. For example, change
580
581 pcre_exec(pattern, extra, subject, length, options, ovec, ovecsize)
582 to
583 pcre_exec(pattern, extra, subject, length, 0, options, ovec, ovecsize)
584
585 ****

Properties

Name Value
svn:eol-style native
svn:keywords "Author Date Id Revision Url"

  ViewVC Help
Powered by ViewVC 1.1.5