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