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