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