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

Contents of /code/trunk/NEWS

Parent Directory Parent Directory | Revision Log Revision Log


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

Properties

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

  ViewVC Help
Powered by ViewVC 1.1.5