Annotation of embedaddon/pcre/ChangeLog, revision 1.1.1.5
1.1 misho 1: ChangeLog for PCRE
2: ------------------
3:
1.1.1.5 ! misho 4: Version 8.34 15-December-2013
! 5: -----------------------------
! 6:
! 7: 1. Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
! 8: executable memory. Patch inspired by Carsten Klein.
! 9:
! 10: 2. ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
! 11: this macro is never tested and has no effect, because the work to support
! 12: coverage involves only compiling and linking options and special targets in
! 13: the Makefile. The comment in config.h implied that defining the macro would
! 14: enable coverage support, which is totally false. There was also support for
! 15: setting this macro in the CMake files (my fault, I just copied it from
! 16: configure). SUPPORT_GCOV has now been removed.
! 17:
! 18: 3. Make a small performance improvement in strlen16() and strlen32() in
! 19: pcretest.
! 20:
! 21: 4. Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
! 22: detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
! 23: these cases). There was also one in pcretest.c.
! 24:
! 25: 5. Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
! 26:
! 27: 6. In UTF mode, the code for checking whether a group could match an empty
! 28: string (which is used for indefinitely repeated groups to allow for
! 29: breaking an infinite loop) was broken when the group contained a repeated
! 30: negated single-character class with a character that occupied more than one
! 31: data item and had a minimum repetition of zero (for example, [^\x{100}]* in
! 32: UTF-8 mode). The effect was undefined: the group might or might not be
! 33: deemed as matching an empty string, or the program might have crashed.
! 34:
! 35: 7. The code for checking whether a group could match an empty string was not
! 36: recognizing that \h, \H, \v, \V, and \R must match a character.
! 37:
! 38: 8. Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
! 39: an empty string. If it can, pcretest shows this in its information output.
! 40:
! 41: 9. Fixed two related bugs that applied to Unicode extended grapheme clusters
! 42: that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
! 43: matched by pcre_exec() without using JIT:
! 44:
! 45: (a) If the rest of the pattern did not match after a maximal run of
! 46: grapheme clusters, the code for backing up to try with fewer of them
! 47: did not always back up over a full grapheme when characters that do not
! 48: have the modifier quality were involved, e.g. Hangul syllables.
! 49:
! 50: (b) If the match point in a subject started with modifier character, and
! 51: there was no match, the code could incorrectly back up beyond the match
! 52: point, and potentially beyond the first character in the subject,
! 53: leading to a segfault or an incorrect match result.
! 54:
! 55: 10. A conditional group with an assertion condition could lead to PCRE
! 56: recording an incorrect first data item for a match if no other first data
! 57: item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
! 58: first data item, and therefore matched "ca" after "c" instead of at the
! 59: start.
! 60:
! 61: 11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
! 62: bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
! 63:
! 64: 12. The source of pcregrep now includes z/OS-specific code so that it can be
! 65: compiled for z/OS as part of the special z/OS distribution.
! 66:
! 67: 13. Added the -T and -TM options to pcretest.
! 68:
! 69: 14. The code in pcre_compile.c for creating the table of named capturing groups
! 70: has been refactored. Instead of creating the table dynamically during the
! 71: actual compiling pass, the information is remembered during the pre-compile
! 72: pass (on the stack unless there are more than 20 named groups, in which
! 73: case malloc() is used) and the whole table is created before the actual
! 74: compile happens. This has simplified the code (it is now nearly 150 lines
! 75: shorter) and prepared the way for better handling of references to groups
! 76: with duplicate names.
! 77:
! 78: 15. A back reference to a named subpattern when there is more than one of the
! 79: same name now checks them in the order in which they appear in the pattern.
! 80: The first one that is set is used for the reference. Previously only the
! 81: first one was inspected. This change makes PCRE more compatible with Perl.
! 82:
! 83: 16. Unicode character properties were updated from Unicode 6.3.0.
! 84:
! 85: 17. The compile-time code for auto-possessification has been refactored, based
! 86: on a patch by Zoltan Herczeg. It now happens after instead of during
! 87: compilation. The code is cleaner, and more cases are handled. The option
! 88: PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
! 89: options in pcretest are provided to set it. It can also be set by
! 90: (*NO_AUTO_POSSESS) at the start of a pattern.
! 91:
! 92: 18. The character VT has been added to the default ("C" locale) set of
! 93: characters that match \s and are generally treated as white space,
! 94: following this same change in Perl 5.18. There is now no difference between
! 95: "Perl space" and "POSIX space". Whether VT is treated as white space in
! 96: other locales depends on the locale.
! 97:
! 98: 19. The code for checking named groups as conditions, either for being set or
! 99: for being recursed, has been refactored (this is related to 14 and 15
! 100: above). Processing unduplicated named groups should now be as fast at
! 101: numerical groups, and processing duplicated groups should be faster than
! 102: before.
! 103:
! 104: 20. Two patches to the CMake build system, by Alexander Barkov:
! 105:
! 106: (1) Replace the "source" command by "." in CMakeLists.txt because
! 107: "source" is a bash-ism.
! 108:
! 109: (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
! 110: without these the CMake build does not work on Solaris.
! 111:
! 112: 21. Perl has changed its handling of \8 and \9. If there is no previously
! 113: encountered capturing group of those numbers, they are treated as the
! 114: literal characters 8 and 9 instead of a binary zero followed by the
! 115: literals. PCRE now does the same.
! 116:
! 117: 22. Following Perl, added \o{} to specify codepoints in octal, making it
! 118: possible to specify values greater than 0777 and also making them
! 119: unambiguous.
! 120:
! 121: 23. Perl now gives an error for missing closing braces after \x{... instead of
! 122: treating the string as literal. PCRE now does the same.
! 123:
! 124: 24. RunTest used to grumble if an inappropriate test was selected explicitly,
! 125: but just skip it when running all tests. This make it awkward to run ranges
! 126: of tests when one of them was inappropriate. Now it just skips any
! 127: inappropriate tests, as it always did when running all tests.
! 128:
! 129: 25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
! 130: character types such as \d or \w, too many callouts were inserted, and the
! 131: data that they returned was rubbish.
! 132:
! 133: 26. In UCP mode, \s was not matching two of the characters that Perl matches,
! 134: namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
! 135: were matched by \h. The code has now been refactored so that the lists of
! 136: the horizontal and vertical whitespace characters used for \h and \v (which
! 137: are defined only in one place) are now also used for \s.
! 138:
! 139: 27. Add JIT support for the 64 bit TileGX architecture.
! 140: Patch by Jiong Wang (Tilera Corporation).
! 141:
! 142: 28. Possessive quantifiers for classes (both explicit and automatically
! 143: generated) now use special opcodes instead of wrapping in ONCE brackets.
! 144:
! 145: 29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
! 146: (because it's meaningless), this was not happening when PCRE_CASELESS was
! 147: set. Not wrong, but inefficient.
! 148:
! 149: 30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
! 150: properties for \w, \d, etc) is present in a test regex. Otherwise if the
! 151: test contains no characters greater than 255, Perl doesn't realise it
! 152: should be using Unicode semantics.
! 153:
! 154: 31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
! 155: [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
! 156: does in Unicode mode.
! 157:
! 158: 32. Added the "forbid" facility to pcretest so that putting tests into the
! 159: wrong test files can sometimes be quickly detected.
! 160:
! 161: 33. There is now a limit (default 250) on the depth of nesting of parentheses.
! 162: This limit is imposed to control the amount of system stack used at compile
! 163: time. It can be changed at build time by --with-parens-nest-limit=xxx or
! 164: the equivalent in CMake.
! 165:
! 166: 34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
! 167: errors. Perl warns for these when in warning mode, but PCRE has no facility
! 168: for giving warnings.
! 169:
! 170: 35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
! 171: However, this was not working for (?!) because it is optimized to (*FAIL),
! 172: for which PCRE does not allow quantifiers. The optimization is now disabled
! 173: when a quantifier follows (?!). I can't see any use for this, but it makes
! 174: things uniform.
! 175:
! 176: 36. Perl no longer allows group names to start with digits, so I have made this
! 177: change also in PCRE. It simplifies the code a bit.
! 178:
! 179: 37. In extended mode, Perl ignores spaces before a + that indicates a
! 180: possessive quantifier. PCRE allowed a space before the quantifier, but not
! 181: before the possessive +. It now does.
! 182:
! 183: 38. The use of \K (reset reported match start) within a repeated possessive
! 184: group such as (a\Kb)*+ was not working.
! 185:
! 186: 40. Document that the same character tables must be used at compile time and
! 187: run time, and that the facility to pass tables to pcre_exec() and
! 188: pcre_dfa_exec() is for use only with saved/restored patterns.
! 189:
! 190: 41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
! 191: features for Builds with MSVC:
! 192:
! 193: 1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
! 194: builds). The .rc files can be used to set FileDescription and many other
! 195: attributes.
! 196:
! 197: 2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
! 198: This allows higher-level build scripts which want .pdb files to avoid
! 199: hard-coding the exact files needed."
! 200:
! 201: 42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
! 202: mean "start of word" and "end of word", respectively, as a transition aid.
! 203:
! 204: 43. A minimizing repeat of a class containing codepoints greater than 255 in
! 205: non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
! 206: compiled to use the heap for recursion.
! 207:
! 208: 44. Got rid of some compiler warnings for unused variables when UTF but not UCP
! 209: is configured.
! 210:
! 211:
1.1.1.4 misho 212: Version 8.33 28-May-2013
1.1.1.5 ! misho 213: ------------------------
1.1.1.4 misho 214:
215: 1. Added 'U' to some constants that are compared to unsigned integers, to
216: avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
217: variables that are added to signed variables, to ensure the result is
218: signed and can be negated.
219:
220: 2. Applied patch by Daniel Richard G for quashing MSVC warnings to the
221: CMake config files.
222:
223: 3. Revise the creation of config.h.generic so that all boolean macros are
224: #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
225: overriding via -D on the command line possible.
226:
227: 4. Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
228: to unsigned int is reported to make a quite noticeable speed difference in
229: a specific Windows environment. Testing on Linux did also appear to show
230: some benefit (and it is clearly not harmful). Also fixed the definition of
231: Xop which should be unsigned.
232:
233: 5. Related to (4), changing the definition of the intermediate variable cc
234: in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
235: improvements.
236:
237: 6. Fix forward search in JIT when link size is 3 or greater. Also removed some
238: unnecessary spaces.
239:
240: 7. Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
241: and later.
242:
243: 8. Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
244:
245: 9. Optimizing fast_forward_start_bits in JIT.
246:
247: 10. Adding support for callouts in JIT, and fixing some issues revealed
248: during this work. Namely:
249:
250: (a) Unoptimized capturing brackets incorrectly reset on backtrack.
251:
252: (b) Minimum length was not checked before the matching is started.
253:
254: 11. The value of capture_last that is passed to callouts was incorrect in some
255: cases when there was a capture on one path that was subsequently abandoned
256: after a backtrack. Also, the capture_last value is now reset after a
257: recursion, since all captures are also reset in this case.
258:
259: 12. The interpreter no longer returns the "too many substrings" error in the
260: case when an overflowing capture is in a branch that is subsequently
261: abandoned after a backtrack.
262:
263: 13. In the pathological case when an offset vector of size 2 is used, pcretest
264: now prints out the matched string after a yield of 0 or 1.
265:
266: 14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
267: Only supported by the JIT compiler at the moment.
268:
269: 15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
270:
271: 16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
272: offset of the starting point of the matching process, provided the offsets
273: vector is large enough.
274:
275: 17. The \A escape now records a lookbehind value of 1, though its execution
276: does not actually inspect the previous character. This is to ensure that,
277: in partial multi-segment matching, at least one character from the old
278: segment is retained when a new segment is processed. Otherwise, if there
279: are no lookbehinds in the pattern, \A might match incorrectly at the start
280: of a new segment.
281:
282: 18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
283:
284: 19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
285: gives some modest performance improvement in 8-bit mode.
286:
287: 20. Added the PCRE-specific property \p{Xuc} for matching characters that can
288: be expressed in certain programming languages using Universal Character
289: Names.
290:
291: 21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
292: which points out that "non characters" are not "characters that may not
293: appear in Unicode strings" but rather "characters that are reserved for
294: internal use and have only local meaning".
295:
296: 22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
297: there was a conditional group that depended on an assertion, if the
298: assertion was false, the callout that immediately followed the alternation
299: in the condition was skipped when pcre_exec() was used for matching.
300:
301: 23. Allow an explicit callout to be inserted before an assertion that is the
302: condition for a conditional group, for compatibility with automatic
303: callouts, which always insert a callout at this point.
304:
305: 24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
306: confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
307:
308: 25. (*PRUNE) is now supported by the JIT compiler.
309:
310: 26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
311:
312: 27. Fix the case where there are two or more SKIPs with arguments that may be
313: ignored.
314:
315: 28. (*SKIP) is now supported by the JIT compiler.
316:
317: 29. (*THEN) is now supported by the JIT compiler.
318:
319: 30. Update RunTest with additional test selector options.
320:
321: 31. The way PCRE handles backtracking verbs has been changed in two ways.
322:
323: (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
324: SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
325: backtracking. In some cases this makes it more Perl-compatible, but Perl's
326: rather obscure rules do not always do the same thing.
327:
328: (2) Previously, backtracking verbs were confined within assertions. This is
329: no longer the case for positive assertions, except for (*ACCEPT). Again,
330: this sometimes improves Perl compatibility, and sometimes does not.
331:
332: 32. A number of tests that were in test 2 because Perl did things differently
333: have been moved to test 1, because either Perl or PCRE has changed, and
334: these tests are now compatible.
335:
336: 32. Backtracking control verbs are now handled in the same way in JIT and
337: interpreter.
338:
339: 33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
340: contained a forward subroutine reference caused a compile error.
341:
342: 34. Auto-detect and optimize limited repetitions in JIT.
343:
344: 35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
345: blocking (*UTF) etc.
346:
347: 36. In the interpreter, maximizing pattern repetitions for characters and
348: character types now use tail recursion, which reduces stack usage.
349:
350: 37. The value of the max lookbehind was not correctly preserved if a compiled
351: and saved regex was reloaded on a host of different endianness.
352:
353: 38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
354: of the compiled pattern block, expand the flags field from 16 to 32 bits
355: because it was almost full.
356:
357: 39. Try madvise first before posix_madvise.
358:
359: 40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
360: with a pattern such as ^$. It has taken 4 years for anybody to notice! The
361: original change locked out all matches of empty strings. This has been
362: changed so that one match of an empty string per line is recognized.
363: Subsequent searches on the same line (for colouring or for --only-matching,
364: for example) do not recognize empty strings.
365:
366: 41. Applied a user patch to fix a number of spelling mistakes in comments.
367:
368: 42. Data lines longer than 65536 caused pcretest to crash.
369:
370: 43. Clarified the data type for length and startoffset arguments for pcre_exec
371: and pcre_dfa_exec in the function-specific man pages, where they were
372: explicitly stated to be in bytes, never having been updated. I also added
373: some clarification to the pcreapi man page.
374:
375: 44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
376: a segmentation fault.
377:
378:
379: Version 8.32 30-November-2012
380: -----------------------------
381:
382: 1. Improved JIT compiler optimizations for first character search and single
383: character iterators.
384:
385: 2. Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
386: Patch by Daniel Richard G.
387:
388: 3. Single character iterator optimizations in the JIT compiler.
389:
390: 4. Improved JIT compiler optimizations for character ranges.
391:
392: 5. Rename the "leave" variable names to "quit" to improve WinCE compatibility.
393: Reported by Giuseppe D'Angelo.
394:
395: 6. The PCRE_STARTLINE bit, indicating that a match can occur only at the start
396: of a line, was being set incorrectly in cases where .* appeared inside
397: atomic brackets at the start of a pattern, or where there was a subsequent
398: *PRUNE or *SKIP.
399:
400: 7. Improved instruction cache flush for POWER/PowerPC.
401: Patch by Daniel Richard G.
402:
403: 8. Fixed a number of issues in pcregrep, making it more compatible with GNU
404: grep:
405:
406: (a) There is now no limit to the number of patterns to be matched.
407:
408: (b) An error is given if a pattern is too long.
409:
410: (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
411: are now supported.
412:
413: (d) --exclude-from and --include-from (multiple use) have been added.
414:
415: (e) Exclusions and inclusions now apply to all files and directories, not
416: just to those obtained from scanning a directory recursively.
417:
418: (f) Multiple uses of -f and --file-list are now supported.
419:
420: (g) In a Windows environment, the default for -d has been changed from
421: "read" (the GNU grep default) to "skip", because otherwise the presence
422: of a directory in the file list provokes an error.
423:
424: (h) The documentation has been revised and clarified in places.
425:
426: 9. Improve the matching speed of capturing brackets.
427:
428: 10. Changed the meaning of \X so that it now matches a Unicode extended
429: grapheme cluster.
430:
431: 11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
432: out POSIX threads when JIT support is configured.
433:
434: 12. Added support for PCRE_STUDY_EXTRA_NEEDED.
435:
436: 13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
437: structure could go wrong in environments where size_t is not the same size
438: as int.
439:
440: 14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
441: set.
442:
443: 15. The EBCDIC support had decayed; later updates to the code had included
444: explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
445: general tidy up of EBCDIC-related issues, and the documentation was also
446: not quite right. There is now a test that can be run on ASCII systems to
447: check some of the EBCDIC-related things (but is it not a full test).
448:
449: 16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
450: in a small tidy to the code.
451:
452: 17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
453:
454: 18. If the --only-matching (-o) option in pcregrep is specified multiple
455: times, each one causes appropriate output. For example, -o1 -o2 outputs the
456: substrings matched by the 1st and 2nd capturing parentheses. A separating
457: string can be specified by --om-separator (default empty).
458:
459: 19. Improving the first n character searches.
460:
461: 20. Turn case lists for horizontal and vertical white space into macros so that
462: they are defined only once.
463:
464: 21. This set of changes together give more compatible Unicode case-folding
465: behaviour for characters that have more than one other case when UCP
466: support is available.
467:
468: (a) The Unicode property table now has offsets into a new table of sets of
469: three or more characters that are case-equivalent. The MultiStage2.py
470: script that generates these tables (the pcre_ucd.c file) now scans
471: CaseFolding.txt instead of UnicodeData.txt for character case
472: information.
473:
474: (b) The code for adding characters or ranges of characters to a character
475: class has been abstracted into a generalized function that also handles
476: case-independence. In UTF-mode with UCP support, this uses the new data
477: to handle characters with more than one other case.
478:
479: (c) A bug that is fixed as a result of (b) is that codepoints less than 256
480: whose other case is greater than 256 are now correctly matched
481: caselessly. Previously, the high codepoint matched the low one, but not
482: vice versa.
483:
484: (d) The processing of \h, \H, \v, and \ in character classes now makes use
485: of the new class addition function, using character lists defined as
486: macros alongside the case definitions of 20 above.
487:
488: (e) Caseless back references now work with characters that have more than
489: one other case.
490:
491: (f) General caseless matching of characters with more than one other case
492: is supported.
493:
494: 22. Unicode character properties were updated from Unicode 6.2.0
495:
496: 23. Improved CMake support under Windows. Patch by Daniel Richard G.
497:
498: 24. Add support for 32-bit character strings, and UTF-32
499:
500: 25. Major JIT compiler update (code refactoring and bugfixing).
501: Experimental Sparc 32 support is added.
502:
503: 26. Applied a modified version of Daniel Richard G's patch to create
504: pcre.h.generic and config.h.generic by "make" instead of in the
505: PrepareRelease script.
506:
507: 27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
508: pcre_compile.c when checking for a zero character.
509:
510: 28. Introducing a native interface for JIT. Through this interface, the compiled
511: machine code can be directly executed. The purpose of this interface is to
512: provide fast pattern matching, so several sanity checks are not performed.
513: However, feature tests are still performed. The new interface provides
514: 1.4x speedup compared to the old one.
515:
516: 29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
517: the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
518: was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
519:
520: 30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
521: greater than 0x7fffffff (which cannot be represented in UTF-8, even under
522: the "old" RFC 2279). Instead, it ended up passing a negative length to
523: pcre_exec().
524:
525: 31. Add support for GCC's visibility feature to hide internal functions.
526:
527: 32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
528: "unknown -C option" after outputting 0 or 1.
529:
530: 33. There is now support for generating a code coverage report for the test
531: suite in environments where gcc is the compiler and lcov is installed. This
532: is mainly for the benefit of the developers.
533:
534: 34. If PCRE is built with --enable-valgrind, certain memory regions are marked
535: unaddressable using valgrind annotations, allowing valgrind to detect
536: invalid memory accesses. This is mainly for the benefit of the developers.
537:
538: 25. (*UTF) can now be used to start a pattern in any of the three libraries.
539:
540: 26. Give configure error if --enable-cpp but no C++ compiler found.
541:
542:
1.1.1.3 misho 543: Version 8.31 06-July-2012
544: -------------------------
545:
546: 1. Fixing a wrong JIT test case and some compiler warnings.
547:
548: 2. Removed a bashism from the RunTest script.
549:
550: 3. Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
551: to unsigned type, result still unsigned" that was given by an MS compiler
552: on encountering the code "-sizeof(xxx)".
553:
554: 4. Partial matching support is added to the JIT compiler.
555:
556: 5. Fixed several bugs concerned with partial matching of items that consist
557: of more than one character:
558:
559: (a) /^(..)\1/ did not partially match "aba" because checking references was
560: done on an "all or nothing" basis. This also applied to repeated
561: references.
562:
563: (b) \R did not give a hard partial match if \r was found at the end of the
564: subject.
565:
566: (c) \X did not give a hard partial match after matching one or more
567: characters at the end of the subject.
568:
569: (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
570: a partial match for the string "\r".
571:
572: (e) When newline was set to CRLF, the metacharacter "." did not recognize
573: a partial match for a CR character at the end of the subject string.
574:
575: 6. If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
576: running pcretest, the text "(JIT)" added to the output whenever JIT is
577: actually used to run the match.
578:
579: 7. Individual JIT compile options can be set in pcretest by following -s+[+]
580: or /S+[+] with a digit between 1 and 7.
581:
582: 8. OP_NOT now supports any UTF character not just single-byte ones.
583:
584: 9. (*MARK) control verb is now supported by the JIT compiler.
585:
586: 10. The command "./RunTest list" lists the available tests without actually
587: running any of them. (Because I keep forgetting what they all are.)
588:
589: 11. Add PCRE_INFO_MAXLOOKBEHIND.
590:
591: 12. Applied a (slightly modified) user-supplied patch that improves performance
592: when the heap is used for recursion (compiled with --disable-stack-for-
593: recursion). Instead of malloc and free for each heap frame each time a
594: logical recursion happens, frames are retained on a chain and re-used where
595: possible. This sometimes gives as much as 30% improvement.
596:
597: 13. As documented, (*COMMIT) is now confined to within a recursive subpattern
598: call.
599:
600: 14. As documented, (*COMMIT) is now confined to within a positive assertion.
601:
602: 15. It is now possible to link pcretest with libedit as an alternative to
603: libreadline.
604:
605: 16. (*COMMIT) control verb is now supported by the JIT compiler.
606:
607: 17. The Unicode data tables have been updated to Unicode 6.1.0.
608:
609: 18. Added --file-list option to pcregrep.
610:
611: 19. Added binary file support to pcregrep, including the -a, --binary-files,
612: -I, and --text options.
613:
614: 20. The madvise function is renamed for posix_madvise for QNX compatibility
615: reasons. Fixed by Giuseppe D'Angelo.
616:
617: 21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
618:
619: 22. Changed the option for creating symbolic links for 16-bit man pages from
620: -s to -sf so that re-installing does not cause issues.
621:
622: 23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
623:
624: 24. Fixed a very old bug in pcretest that caused errors with restarted DFA
625: matches in certain environments (the workspace was not being correctly
626: retained). Also added to pcre_dfa_exec() a simple plausibility check on
627: some of the workspace data at the beginning of a restart.
628:
629: 25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
630: was not doing so when it should - probably a typo introduced by SVN 528
631: (change 8.10/14).
632:
633: 26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
634: \w+ when the character tables indicated that \x{c4} was a word character.
635: There were several related cases, all because the tests for doing a table
636: lookup were testing for characters less than 127 instead of 255.
637:
638: 27. If a pattern contains capturing parentheses that are not used in a match,
639: their slots in the ovector are set to -1. For those that are higher than
640: any matched groups, this happens at the end of processing. In the case when
641: there were back references that the ovector was too small to contain
642: (causing temporary malloc'd memory to be used during matching), and the
643: highest capturing number was not used, memory off the end of the ovector
644: was incorrectly being set to -1. (It was using the size of the temporary
645: memory instead of the true size.)
646:
647: 28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
648: ovector size, it uses memory at the end of the block that it has got.
649:
650: 29. Check for an overlong MARK name and give an error at compile time. The
651: limit is 255 for the 8-bit library and 65535 for the 16-bit library.
652:
653: 30. JIT compiler update.
654:
655: 31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
656: Rill for the patch.
657:
658: 32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
659:
660: 33. Variable renamings in the PCRE-JIT compiler. No functionality change.
661:
662: 34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
663: SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
664: was enabled.
665:
666: 35. Improve JIT code generation for greedy plus quantifier.
667:
668: 36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
669: 1 to "aa" instead of to an empty string. The bug affected repeated groups
670: that could potentially match an empty string.
671:
672: 37. Optimizing single character iterators in JIT.
673:
674: 38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
675: the same checks as \x{...} characters in non-JavaScript mode. Specifically,
676: codepoints that are too big for the mode are faulted, and in a UTF mode,
677: disallowed codepoints are also faulted.
678:
679: 39. If PCRE was compiled with UTF support, in three places in the DFA
680: matcher there was code that should only have been obeyed in UTF mode, but
681: was being obeyed unconditionally. In 8-bit mode this could cause incorrect
682: processing when bytes with values greater than 127 were present. In 16-bit
683: mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
684: both cases the values are those that cannot be the first data item in a UTF
685: character. The three items that might have provoked this were recursions,
686: possessively repeated groups, and atomic groups.
687:
688: 40. Ensure that libpcre is explicitly listed in the link commands for pcretest
689: and pcregrep, because some OS require shared objects to be explicitly
690: passed to ld, causing the link step to fail if they are not.
691:
692: 41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
693: mode, patterns that started with \h* or \R* might be incorrectly matched.
694:
695:
1.1.1.2 misho 696: Version 8.30 04-February-2012
697: -----------------------------
698:
699: 1. Renamed "isnumber" as "is_a_number" because in some Mac environments this
700: name is defined in ctype.h.
701:
702: 2. Fixed a bug in fixed-length calculation for lookbehinds that would show up
703: only in quite long subpatterns.
704:
705: 3. Removed the function pcre_info(), which has been obsolete and deprecated
706: since it was replaced by pcre_fullinfo() in February 2000.
707:
708: 4. For a non-anchored pattern, if (*SKIP) was given with a name that did not
709: match a (*MARK), and the match failed at the start of the subject, a
710: reference to memory before the start of the subject could occur. This bug
711: was introduced by fix 17 of release 8.21.
712:
713: 5. A reference to an unset group with zero minimum repetition was giving
714: totally wrong answers (in non-JavaScript-compatibility mode). For example,
715: /(another)?(\1?)test/ matched against "hello world test". This bug was
716: introduced in release 8.13.
717:
718: 6. Add support for 16-bit character strings (a large amount of work involving
719: many changes and refactorings).
720:
721: 7. RunGrepTest failed on msys because \r\n was replaced by whitespace when the
722: command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
723: from a file.
724:
725: 8. Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
726: rounding is not applied in this particular case).
727:
728: 9. The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
729: if they appear, or are escaped, in patterns.
730:
731: 10. Get rid of a number of -Wunused-but-set-variable warnings.
732:
733: 11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
734: "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
735: Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
736: also returns the mark "x". This bug applied to capturing parentheses,
737: non-capturing parentheses, and atomic parentheses. It also applied to some
738: assertions.
739:
740: 12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
741: information out of configure.ac instead of relying on pcre.h.generic, which
742: is not stored in the repository.
743:
744: 13. Applied Dmitry V. Levin's patch for a more portable method for linking with
745: -lreadline.
746:
747: 14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
748:
749: 15. Applied Graycode's patch to put the top-level frame on the stack rather
750: than the heap when not using the stack for recursion. This gives a
751: performance improvement in many cases when recursion is not deep.
752:
753: 16. Experimental code added to "pcretest -C" to output the stack frame size.
754:
755:
1.1 misho 756: Version 8.21 12-Dec-2011
757: ------------------------
758:
759: 1. Updating the JIT compiler.
760:
761: 2. JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
762: are added as well.
763:
764: 3. Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
765: PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
766: calling _pcre_jit_exec. Some extra comments are added.
767:
768: 4. (*MARK) settings inside atomic groups that do not contain any capturing
769: parentheses, for example, (?>a(*:m)), were not being passed out. This bug
770: was introduced by change 18 for 8.20.
771:
772: 5. Supporting of \x, \U and \u in JavaScript compatibility mode based on the
773: ECMA-262 standard.
774:
775: 6. Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
776: erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
777: This bug was probably introduced by change 9 of 8.13.
778:
779: 7. While fixing 6 above, I noticed that a number of other items were being
780: incorrectly rejected as "not fixed length". This arose partly because newer
781: opcodes had not been added to the fixed-length checking code. I have (a)
782: corrected the bug and added tests for these items, and (b) arranged for an
783: error to occur if an unknown opcode is encountered while checking for fixed
784: length instead of just assuming "not fixed length". The items that were
785: rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
786: (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
787: repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
788:
789: 8. A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
790: being incorrectly compiled and would have given unpredicatble results.
791:
792: 9. A possessively repeated subpattern with minimum repeat count greater than
793: one behaved incorrectly. For example, (A){2,}+ behaved as if it was
794: (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
795: the first (A) could occur when it should not.
796:
797: 10. Add a cast and remove a redundant test from the code.
798:
799: 11. JIT should use pcre_malloc/pcre_free for allocation.
800:
801: 12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
802: best practice nowadays, and helps with cross-compiling. (If the exec_prefix
803: is anything other than /usr, -L is still shown).
804:
805: 13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
806:
807: 14. Perl does not support \N without a following name in a [] class; PCRE now
808: also gives an error.
809:
810: 15. If a forward reference was repeated with an upper limit of around 2000,
811: it caused the error "internal error: overran compiling workspace". The
812: maximum number of forward references (including repeats) was limited by the
813: internal workspace, and dependent on the LINK_SIZE. The code has been
814: rewritten so that the workspace expands (via pcre_malloc) if necessary, and
815: the default depends on LINK_SIZE. There is a new upper limit (for safety)
816: of around 200,000 forward references. While doing this, I also speeded up
817: the filling in of repeated forward references.
818:
819: 16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
820: incorrectly expecting the subject to contain another "a" after the start.
821:
822: 17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
823: in the match, the SKIP should be ignored. This was not happening; instead
824: the SKIP was being treated as NOMATCH. For patterns such as
825: /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
826: tested.
827:
828: 18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
829: now much more compatible with Perl, in particular in cases where the result
830: is a non-match for a non-anchored pattern. For example, if
831: /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
832: "m", where previously it did not return a name. A side effect of this
833: change is that for partial matches, the last encountered mark name is
834: returned, as for non matches. A number of tests that were previously not
835: Perl-compatible have been moved into the Perl-compatible test files. The
836: refactoring has had the pleasing side effect of removing one argument from
837: the match() function, thus reducing its stack requirements.
838:
839: 19. If the /S+ option was used in pcretest to study a pattern using JIT,
840: subsequent uses of /S (without +) incorrectly behaved like /S+.
841:
842: 21. Retrieve executable code size support for the JIT compiler and fixing
843: some warnings.
844:
845: 22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
846: not work when the shorter character appeared right at the end of the
847: subject string.
848:
849: 23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
850: systems.
851:
852: 24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
853: output it when the /M option is used in pcretest.
854:
855: 25. The CheckMan script was not being included in the distribution. Also, added
856: an explicit "perl" to run Perl scripts from the PrepareRelease script
857: because this is reportedly needed in Windows.
858:
859: 26. If study data was being save in a file and studying had not found a set of
860: "starts with" bytes for the pattern, the data written to the file (though
861: never used) was taken from uninitialized memory and so caused valgrind to
862: complain.
863:
864: 27. Updated RunTest.bat as provided by Sheri Pierce.
865:
866: 28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
867:
868: 29. Computation of memory usage for the table of capturing group names was
869: giving an unnecessarily large value.
870:
871:
872: Version 8.20 21-Oct-2011
873: ------------------------
874:
875: 1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
876: a POSIX class. After further experiments with Perl, which convinced me that
877: Perl has bugs and confusions, a closing square bracket is no longer allowed
878: in a POSIX name. This bug also affected patterns with classes that started
879: with full stops.
880:
881: 2. If a pattern such as /(a)b|ac/ is matched against "ac", there is no
882: captured substring, but while checking the failing first alternative,
883: substring 1 is temporarily captured. If the output vector supplied to
884: pcre_exec() was not big enough for this capture, the yield of the function
885: was still zero ("insufficient space for captured substrings"). This cannot
886: be totally fixed without adding another stack variable, which seems a lot
887: of expense for a edge case. However, I have improved the situation in cases
888: such as /(a)(b)x|abc/ matched against "abc", where the return code
889: indicates that fewer than the maximum number of slots in the ovector have
890: been set.
891:
892: 3. Related to (2) above: when there are more back references in a pattern than
893: slots in the output vector, pcre_exec() uses temporary memory during
894: matching, and copies in the captures as far as possible afterwards. It was
895: using the entire output vector, but this conflicts with the specification
896: that only 2/3 is used for passing back captured substrings. Now it uses
897: only the first 2/3, for compatibility. This is, of course, another edge
898: case.
899:
900: 4. Zoltan Herczeg's just-in-time compiler support has been integrated into the
901: main code base, and can be used by building with --enable-jit. When this is
902: done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
903: runtime --no-jit option is given.
904:
905: 5. When the number of matches in a pcre_dfa_exec() run exactly filled the
906: ovector, the return from the function was zero, implying that there were
907: other matches that did not fit. The correct "exactly full" value is now
908: returned.
909:
910: 6. If a subpattern that was called recursively or as a subroutine contained
911: (*PRUNE) or any other control that caused it to give a non-standard return,
912: invalid errors such as "Error -26 (nested recursion at the same subject
913: position)" or even infinite loops could occur.
914:
915: 7. If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
916: computing the minimum length on reaching *ACCEPT, and so ended up with the
917: wrong value of 1 rather than 0. Further investigation indicates that
918: computing a minimum subject length in the presence of *ACCEPT is difficult
919: (think back references, subroutine calls), and so I have changed the code
920: so that no minimum is registered for a pattern that contains *ACCEPT.
921:
922: 8. If (*THEN) was present in the first (true) branch of a conditional group,
923: it was not handled as intended. [But see 16 below.]
924:
925: 9. Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
926: Sheri Pierce.
927:
928: 10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
929: the first byte in a match must be "a".
930:
931: 11. Change 17 for 8.13 increased the recursion depth for patterns like
932: /a(?:.)*?a/ drastically. I've improved things by remembering whether a
933: pattern contains any instances of (*THEN). If it does not, the old
934: optimizations are restored. It would be nice to do this on a per-group
935: basis, but at the moment that is not feasible.
936:
937: 12. In some environments, the output of pcretest -C is CRLF terminated. This
938: broke RunTest's code that checks for the link size. A single white space
939: character after the value is now allowed for.
940:
941: 13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
942: For "fr", it uses the Windows-specific input and output files.
943:
944: 14. If (*THEN) appeared in a group that was called recursively or as a
945: subroutine, it did not work as intended. [But see next item.]
946:
947: 15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
948: pattern fragments (but not containing any | characters). If A and B are
949: matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
950: was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
951: D. In other words, Perl considers parentheses that do not contain any |
952: characters to be part of a surrounding alternative, whereas PCRE was
953: treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
954: differently. PCRE now behaves in the same way as Perl, except in the case
955: of subroutine/recursion calls such as (?1) which have in any case always
956: been different (but PCRE had them first :-).
957:
958: 16. Related to 15 above: Perl does not treat the | in a conditional group as
959: creating alternatives. Such a group is treated in the same way as an
960: ordinary group without any | characters when processing (*THEN). PCRE has
961: been changed to match Perl's behaviour.
962:
963: 17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
964: RunGrepTest script failed.
965:
966: 18. Change 22 for version 13 caused atomic groups to use more stack. This is
967: inevitable for groups that contain captures, but it can lead to a lot of
968: stack use in large patterns. The old behaviour has been restored for atomic
969: groups that do not contain any capturing parentheses.
970:
971: 19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
972: suppress the check for a minimum subject length at run time. (If it was
973: given to pcre_exec() or pcre_dfa_exec() it did work.)
974:
975: 20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
976: fail to work when decoding hex characters in data strings in EBCDIC
977: environments.
978:
979: 21. It appears that in at least one Mac OS environment, the isxdigit() function
980: is implemented as a macro that evaluates to its argument more than once,
981: contravening the C 90 Standard (I haven't checked a later standard). There
982: was an instance in pcretest which caused it to go wrong when processing
983: \x{...} escapes in subject strings. The has been rewritten to avoid using
984: things like p++ in the argument of isxdigit().
985:
986:
987: Version 8.13 16-Aug-2011
988: ------------------------
989:
990: 1. The Unicode data tables have been updated to Unicode 6.0.0.
991:
992: 2. Two minor typos in pcre_internal.h have been fixed.
993:
994: 3. Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
995: pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
996: in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
997:
998: 4. There were a number of related bugs in the code for matching backrefences
999: caselessly in UTF-8 mode when codes for the characters concerned were
1000: different numbers of bytes. For example, U+023A and U+2C65 are an upper
1001: and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
1002: (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
1003: code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
1004: 2-byte code at the end of the subject (it thought there wasn't enough data
1005: left).
1006:
1007: 5. Comprehensive information about what went wrong is now returned by
1008: pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
1009: as the output vector has at least 2 elements. The offset of the start of
1010: the failing character and a reason code are placed in the vector.
1011:
1012: 6. When the UTF-8 string check fails for pcre_compile(), the offset that is
1013: now returned is for the first byte of the failing character, instead of the
1014: last byte inspected. This is an incompatible change, but I hope it is small
1015: enough not to be a problem. It makes the returned offset consistent with
1016: pcre_exec() and pcre_dfa_exec().
1017:
1018: 7. pcretest now gives a text phrase as well as the error number when
1019: pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
1020: failure, the offset and reason code are output.
1021:
1022: 8. When \R was used with a maximizing quantifier it failed to skip backwards
1023: over a \r\n pair if the subsequent match failed. Instead, it just skipped
1024: back over a single character (\n). This seems wrong (because it treated the
1025: two characters as a single entity when going forwards), conflicts with the
1026: documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
1027: behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
1028: has been changed.
1029:
1030: 9. Some internal refactoring has changed the processing so that the handling
1031: of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
1032: time (the PCRE_DOTALL option was changed this way some time ago: version
1033: 7.7 change 16). This has made it possible to abolish the OP_OPT op code,
1034: which was always a bit of a fudge. It also means that there is one less
1035: argument for the match() function, which reduces its stack requirements
1036: slightly. This change also fixes an incompatibility with Perl: the pattern
1037: (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
1038:
1039: 10. More internal refactoring has drastically reduced the number of recursive
1040: calls to match() for possessively repeated groups such as (abc)++ when
1041: using pcre_exec().
1042:
1043: 11. While implementing 10, a number of bugs in the handling of groups were
1044: discovered and fixed:
1045:
1046: (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
1047: (a|)*(?1) gave a compile-time internal error.
1048: ((a|)+)+ did not notice that the outer group could match an empty string.
1049: (^a|^)+ was not marked as anchored.
1050: (.*a|.*)+ was not marked as matching at start or after a newline.
1051:
1052: 12. Yet more internal refactoring has removed another argument from the match()
1053: function. Special calls to this function are now indicated by setting a
1054: value in a variable in the "match data" data block.
1055:
1056: 13. Be more explicit in pcre_study() instead of relying on "default" for
1057: opcodes that mean there is no starting character; this means that when new
1058: ones are added and accidentally left out of pcre_study(), testing should
1059: pick them up.
1060:
1061: 14. The -s option of pcretest has been documented for ages as being an old
1062: synonym of -m (show memory usage). I have changed it to mean "force study
1063: for every regex", that is, assume /S for every regex. This is similar to -i
1064: and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1065: using it. It makes it easier to run collections of tests with and without
1066: study enabled, and thereby test pcre_study() more easily. All the standard
1067: tests are now run with and without -s (but some patterns can be marked as
1068: "never study" - see 20 below).
1069:
1070: 15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1071: restoration of the capturing data to the outer values was not happening
1072: correctly.
1073:
1074: 16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1075: empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1076: pattern had matched an empty string, and so incorrectly returned a no
1077: match.
1078:
1079: 17. There was optimizing code for the last branch of non-capturing parentheses,
1080: and also for the obeyed branch of a conditional subexpression, which used
1081: tail recursion to cut down on stack usage. Unfortunately, now that there is
1082: the possibility of (*THEN) occurring in these branches, tail recursion is
1083: no longer possible because the return has to be checked for (*THEN). These
1084: two optimizations have therefore been removed. [But see 8.20/11 above.]
1085:
1086: 18. If a pattern containing \R was studied, it was assumed that \R always
1087: matched two bytes, thus causing the minimum subject length to be
1088: incorrectly computed because \R can also match just one byte.
1089:
1090: 19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1091: was incorrectly computed.
1092:
1093: 20. If /S is present twice on a test pattern in pcretest input, it now
1094: *disables* studying, thereby overriding the use of -s on the command line
1095: (see 14 above). This is necessary for one or two tests to keep the output
1096: identical in both cases.
1097:
1098: 21. When (*ACCEPT) was used in an assertion that matched an empty string and
1099: PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1100:
1101: 22. When an atomic group that contained a capturing parenthesis was
1102: successfully matched, but the branch in which it appeared failed, the
1103: capturing was not being forgotten if a higher numbered group was later
1104: captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1105: group 1 to "a", when in fact it should be unset. This applied to multi-
1106: branched capturing and non-capturing groups, repeated or not, and also to
1107: positive assertions (capturing in negative assertions does not happen
1108: in PCRE) and also to nested atomic groups.
1109:
1110: 23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1111: subject after a captured substring, to make it easier to tell which of a
1112: number of identical substrings has been captured.
1113:
1114: 24. The way atomic groups are processed by pcre_exec() has been changed so that
1115: if they are repeated, backtracking one repetition now resets captured
1116: values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1117: "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1118: "aaa". Previously, it would have been "a". As part of this code
1119: refactoring, the way recursive calls are handled has also been changed.
1120:
1121: 25. If an assertion condition captured any substrings, they were not passed
1122: back unless some other capturing happened later. For example, if
1123: (?(?=(a))a) was matched against "a", no capturing was returned.
1124:
1125: 26. When studying a pattern that contained subroutine calls or assertions,
1126: the code for finding the minimum length of a possible match was handling
1127: direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1128: group 1 called group 2 while simultaneously a separate group 2 called group
1129: 1). A stack overflow occurred in this case. I have fixed this by limiting
1130: the recursion depth to 10.
1131:
1132: 27. Updated RunTest.bat in the distribution to the version supplied by Tom
1133: Fortmann. This supports explicit test numbers on the command line, and has
1134: argument validation and error reporting.
1135:
1136: 28. An instance of \X with an unlimited repeat could fail if at any point the
1137: first character it looked at was a mark character.
1138:
1139: 29. Some minor code refactoring concerning Unicode properties and scripts
1140: should reduce the stack requirement of match() slightly.
1141:
1142: 30. Added the '=' option to pcretest to check the setting of unused capturing
1143: slots at the end of the pattern, which are documented as being -1, but are
1144: not included in the return count.
1145:
1146: 31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1147: compiled something random. Now it gives a compile-time error (as does
1148: Perl).
1149:
1150: 32. A *MARK encountered during the processing of a positive assertion is now
1151: recorded and passed back (compatible with Perl).
1152:
1153: 33. If --only-matching or --colour was set on a pcregrep call whose pattern
1154: had alternative anchored branches, the search for a second match in a line
1155: was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1156: matched the line "0102" twice. The same bug affected patterns that started
1157: with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1158: twice.
1159:
1160: 34. Previously, PCRE did not allow quantification of assertions. However, Perl
1161: does, and because of capturing effects, quantifying parenthesized
1162: assertions may at times be useful. Quantifiers are now allowed for
1163: parenthesized assertions.
1164:
1165: 35. A minor code tidy in pcre_compile() when checking options for \R usage.
1166:
1167: 36. \g was being checked for fancy things in a character class, when it should
1168: just be a literal "g".
1169:
1170: 37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1171: appearance of a nested POSIX class supersedes an apparent external class.
1172: For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1173: unescaped square brackets may also appear as part of class names. For
1174: example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1175: more like Perl. (But see 8.20/1 above.)
1176:
1177: 38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1178: was because it thought it was \N{name}, which is not supported).
1179:
1180: 39. Add minix to OS list not supporting the -S option in pcretest.
1181:
1182: 40. PCRE tries to detect cases of infinite recursion at compile time, but it
1183: cannot analyze patterns in sufficient detail to catch mutual recursions
1184: such as ((?1))((?2)). There is now a runtime test that gives an error if a
1185: subgroup is called recursively as a subpattern for a second time at the
1186: same position in the subject string. In previous releases this might have
1187: been caught by the recursion limit, or it might have run out of stack.
1188:
1189: 41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1190: happen only once. PCRE was, however incorrectly giving a compile time error
1191: "recursive call could loop indefinitely" because it cannot analyze the
1192: pattern in sufficient detail. The compile time test no longer happens when
1193: PCRE is compiling a conditional subpattern, but actual runaway loops are
1194: now caught at runtime (see 40 above).
1195:
1196: 42. It seems that Perl allows any characters other than a closing parenthesis
1197: to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1198: has been changed to be the same.
1199:
1200: 43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1201: as not to get warnings when autogen.sh is called. Also changed
1202: AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1203:
1204: 44. To help people who use pcregrep to scan files containing exceedingly long
1205: lines, the following changes have been made:
1206:
1207: (a) The default value of the buffer size parameter has been increased from
1208: 8K to 20K. (The actual buffer used is three times this size.)
1209:
1210: (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1211: PCRE is built.
1212:
1213: (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1214: to be set at run time.
1215:
1216: (d) Numerical values in pcregrep options can be followed by K or M, for
1217: example --buffer-size=50K.
1218:
1219: (e) If a line being scanned overflows pcregrep's buffer, an error is now
1220: given and the return code is set to 2.
1221:
1222: 45. Add a pointer to the latest mark to the callout data block.
1223:
1224: 46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1225: partial match of an empty string instead of no match. This was specific to
1226: the use of ".".
1227:
1228: 47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1229: complete match instead of a partial match. This bug was dependent on both
1230: the PCRE_UTF8 and PCRE_DOTALL options being set.
1231:
1232: 48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1233: starting byte set, because \b was not being ignored.
1234:
1235:
1236: Version 8.12 15-Jan-2011
1237: ------------------------
1238:
1239: 1. Fixed some typos in the markup of the man pages, and wrote a script that
1240: checks for such things as part of the documentation building process.
1241:
1242: 2. On a big-endian 64-bit system, pcregrep did not correctly process the
1243: --match-limit and --recursion-limit options (added for 8.11). In
1244: particular, this made one of the standard tests fail. (The integer value
1245: went into the wrong half of a long int.)
1246:
1247: 3. If the --colour option was given to pcregrep with -v (invert match), it
1248: did strange things, either producing crazy output, or crashing. It should,
1249: of course, ignore a request for colour when reporting lines that do not
1250: match.
1251:
1252: 4. Another pcregrep bug caused similar problems if --colour was specified with
1253: -M (multiline) and the pattern match finished with a line ending.
1254:
1255: 5. In pcregrep, when a pattern that ended with a literal newline sequence was
1256: matched in multiline mode, the following line was shown as part of the
1257: match. This seems wrong, so I have changed it.
1258:
1259: 6. Another pcregrep bug in multiline mode, when --colour was specified, caused
1260: the check for further matches in the same line (so they could be coloured)
1261: to overrun the end of the current line. If another match was found, it was
1262: incorrectly shown (and then shown again when found in the next line).
1263:
1264: 7. If pcregrep was compiled under Windows, there was a reference to the
1265: function pcregrep_exit() before it was defined. I am assuming this was
1266: the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1267: reported by a user. I've moved the definition above the reference.
1268:
1269:
1270: Version 8.11 10-Dec-2010
1271: ------------------------
1272:
1273: 1. (*THEN) was not working properly if there were untried alternatives prior
1274: to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1275: backtracked to try for "b" instead of moving to the next alternative branch
1276: at the same level (in this case, to look for "c"). The Perl documentation
1277: is clear that when (*THEN) is backtracked onto, it goes to the "next
1278: alternative in the innermost enclosing group".
1279:
1280: 2. (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1281: such as (A(*COMMIT)B(*THEN)C|D) any failure after matching A should
1282: result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1283: (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1284: (*THEN).
1285:
1286: 3. If \s appeared in a character class, it removed the VT character from
1287: the class, even if it had been included by some previous item, for example
1288: in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1289: of \s, but is part of the POSIX "space" class.)
1290:
1291: 4. A partial match never returns an empty string (because you can always
1292: match an empty string at the end of the subject); however the checking for
1293: an empty string was starting at the "start of match" point. This has been
1294: changed to the "earliest inspected character" point, because the returned
1295: data for a partial match starts at this character. This means that, for
1296: example, /(?<=abc)def/ gives a partial match for the subject "abc"
1297: (previously it gave "no match").
1298:
1299: 5. Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1300: of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1301: previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1302: has an implication that the given string is incomplete (because a partial
1303: match is preferred over a full match). For this reason, these items now
1304: give a partial match in this situation. [Aside: previously, the one case
1305: /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1306: match rather than a full match, which was wrong by the old rules, but is
1307: now correct.]
1308:
1309: 6. There was a bug in the handling of #-introduced comments, recognized when
1310: PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1311: If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1312: UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1313: scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1314: but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1315: places in pcre_compile().
1316:
1317: 7. Related to (6) above, when pcre_compile() was skipping #-introduced
1318: comments when looking ahead for named forward references to subpatterns,
1319: the only newline sequence it recognized was NL. It now handles newlines
1320: according to the set newline convention.
1321:
1322: 8. SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1323: former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1324: cater for a lack of strerror(). These oversights have been fixed.
1325:
1326: 9. Added --match-limit and --recursion-limit to pcregrep.
1327:
1328: 10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1329:
1330: 11. When the -o option was used, pcregrep was setting a return code of 1, even
1331: when matches were found, and --line-buffered was not being honoured.
1332:
1333: 12. Added an optional parentheses number to the -o and --only-matching options
1334: of pcregrep.
1335:
1336: 13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1337: can match an empty string. The code to do it in pcretest and pcredemo
1338: needed fixing:
1339:
1340: (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1341: only one byte after an empty string match just before CRLF (this case
1342: just got forgotten; "any" and "anycrlf" were OK).
1343:
1344: (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1345: mode when an empty string match preceded an ASCII character followed by
1346: a non-ASCII character. (The code for advancing by one character rather
1347: than one byte was nonsense.)
1348:
1349: (c) The pcredemo.c sample program did not have any code at all to handle
1350: the cases when CRLF is a valid newline sequence.
1351:
1352: 14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1353: as a starting offset was within the subject string. There is now a new
1354: error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1355: negative or greater than the length of the string. In order to test this,
1356: pcretest is extended to allow the setting of negative starting offsets.
1357:
1358: 15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1359: starting offset points to the beginning of a UTF-8 character was
1360: unnecessarily clumsy. I tidied it up.
1361:
1362: 16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1363: bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1364:
1365: 17. Nobody had reported that the --include_dir option, which was added in
1366: release 7.7 should have been called --include-dir (hyphen, not underscore)
1367: for compatibility with GNU grep. I have changed it to --include-dir, but
1368: left --include_dir as an undocumented synonym, and the same for
1369: --exclude-dir, though that is not available in GNU grep, at least as of
1370: release 2.5.4.
1371:
1372: 18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1373: characters from a string of bytes) have been redefined so as not to use
1374: loops, in order to improve performance in some environments. At the same
1375: time, I abstracted some of the common code into auxiliary macros to save
1376: repetition (this should not affect the compiled code).
1377:
1378: 19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1379: compile-time error is now given if \c is not followed by an ASCII
1380: character, that is, a byte less than 128. (In EBCDIC mode, the code is
1381: different, and any byte value is allowed.)
1382:
1383: 20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1384: START_OPTIMIZE option, which is now allowed at compile time - but just
1385: passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1386: to pcregrep and other applications that have no direct access to PCRE
1387: options. The new /Y option in pcretest sets this option when calling
1388: pcre_compile().
1389:
1390: 21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1391: back references. Groups containing recursive back references were forced to
1392: be atomic by that change, but in the case of named groups, the amount of
1393: memory required was incorrectly computed, leading to "Failed: internal
1394: error: code overflow". This has been fixed.
1395:
1396: 22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1397: pcretest.c, to avoid build problems in some Borland environments.
1398:
1399:
1400: Version 8.10 25-Jun-2010
1401: ------------------------
1402:
1403: 1. Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1404: THEN.
1405:
1406: 2. (*ACCEPT) was not working when inside an atomic group.
1407:
1408: 3. Inside a character class, \B is treated as a literal by default, but
1409: faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1410: causes the error). The code is unchanged, but I tidied the documentation.
1411:
1412: 4. Inside a character class, PCRE always treated \R and \X as literals,
1413: whereas Perl faults them if its -w option is set. I have changed PCRE so
1414: that it faults them when PCRE_EXTRA is set.
1415:
1416: 5. Added support for \N, which always matches any character other than
1417: newline. (It is the same as "." when PCRE_DOTALL is not set.)
1418:
1419: 6. When compiling pcregrep with newer versions of gcc which may have
1420: FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1421: declared with attribute warn_unused_result" were given. Just casting the
1422: result to (void) does not stop the warnings; a more elaborate fudge is
1423: needed. I've used a macro to implement this.
1424:
1425: 7. Minor change to pcretest.c to avoid a compiler warning.
1426:
1427: 8. Added four artifical Unicode properties to help with an option to make
1428: \s etc use properties (see next item). The new properties are: Xan
1429: (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1430:
1431: 9. Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1432: use Unicode properties. (*UCP) at the start of a pattern can be used to set
1433: this option. Modified pcretest to add /W to test this facility. Added
1434: REG_UCP to make it available via the POSIX interface.
1435:
1436: 10. Added --line-buffered to pcregrep.
1437:
1438: 11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1439: studied, and the match started with a letter with a code point greater than
1440: 127 whose first byte was different to the first byte of the other case of
1441: the letter, the other case of this starting letter was not recognized
1442: (#976).
1443:
1444: 12. If a pattern that was studied started with a repeated Unicode property
1445: test, for example, \p{Nd}+, there was the theoretical possibility of
1446: setting up an incorrect bitmap of starting bytes, but fortunately it could
1447: not have actually happened in practice until change 8 above was made (it
1448: added property types that matched character-matching opcodes).
1449:
1450: 13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1451: possible starting bytes for non-anchored patterns.
1452:
1453: 14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1454: \R, and also a number of cases that involve Unicode properties, both
1455: explicit and implicit when PCRE_UCP is set.
1456:
1457: 15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1458: input, it could crash or give wrong results if characters with values
1459: greater than 0xc0 were present in the subject string. (Detail: it assumed
1460: UTF-8 input when processing these items.)
1461:
1462: 16. Added a lot of (int) casts to avoid compiler warnings in systems where
1463: size_t is 64-bit (#991).
1464:
1465: 17. Added a check for running out of memory when PCRE is compiled with
1466: --disable-stack-for-recursion (#990).
1467:
1468: 18. If the last data line in a file for pcretest does not have a newline on
1469: the end, a newline was missing in the output.
1470:
1471: 19. The default pcre_chartables.c file recognizes only ASCII characters (values
1472: less than 128) in its various bitmaps. However, there is a facility for
1473: generating tables according to the current locale when PCRE is compiled. It
1474: turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1475: characters, are recognized by isspace() and therefore were getting set in
1476: these tables, and indeed these tables seem to approximate to ISO 8859. This
1477: caused a problem in UTF-8 mode when pcre_study() was used to create a list
1478: of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1479: which of course cannot start UTF-8 characters. I have changed the code so
1480: that only real ASCII characters (less than 128) and the correct starting
1481: bytes for UTF-8 encodings are set for characters greater than 127 when in
1482: UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1483: altogether.)
1484:
1485: 20. Added the /T option to pcretest so as to be able to run tests with non-
1486: standard character tables, thus making it possible to include the tests
1487: used for 19 above in the standard set of tests.
1488:
1489: 21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1490: reference to a subpattern the other side of a comment that contains an
1491: opening parenthesis caused either an internal compiling error, or a
1492: reference to the wrong subpattern.
1493:
1494:
1495: Version 8.02 19-Mar-2010
1496: ------------------------
1497:
1498: 1. The Unicode data tables have been updated to Unicode 5.2.0.
1499:
1500: 2. Added the option --libs-cpp to pcre-config, but only when C++ support is
1501: configured.
1502:
1503: 3. Updated the licensing terms in the pcregexp.pas file, as agreed with the
1504: original author of that file, following a query about its status.
1505:
1506: 4. On systems that do not have stdint.h (e.g. Solaris), check for and include
1507: inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1508:
1509: 5. A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1510: quantifier applied to a forward-referencing subroutine call, could compile
1511: incorrect code or give the error "internal error: previously-checked
1512: referenced subpattern not found".
1513:
1514: 6. Both MS Visual Studio and Symbian OS have problems with initializing
1515: variables to point to external functions. For these systems, therefore,
1516: pcre_malloc etc. are now initialized to local functions that call the
1517: relevant global functions.
1518:
1519: 7. There were two entries missing in the vectors called coptable and poptable
1520: in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1521: I've fixed the data, and added a kludgy way of testing at compile time that
1522: the lengths are correct (equal to the number of opcodes).
1523:
1524: 8. Following on from 7, I added a similar kludge to check the length of the
1525: eint vector in pcreposix.c.
1526:
1527: 9. Error texts for pcre_compile() are held as one long string to avoid too
1528: much relocation at load time. To find a text, the string is searched,
1529: counting zeros. There was no check for running off the end of the string,
1530: which could happen if a new error number was added without updating the
1531: string.
1532:
1533: 10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1534:
1535: 11. \K was not working if it appeared in an atomic group or in a group that
1536: was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1537: \K is "not well defined" if used in an assertion. PCRE now accepts it if
1538: the assertion is positive, but not if it is negative.
1539:
1540: 12. Change 11 fortuitously reduced the size of the stack frame used in the
1541: "match()" function of pcre_exec.c by one pointer. Forthcoming
1542: implementation of support for (*MARK) will need an extra pointer on the
1543: stack; I have reserved it now, so that the stack frame size does not
1544: decrease.
1545:
1546: 13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1547: item in branch that calls a recursion is a subroutine call - as in the
1548: second branch in the above example - was incorrectly given the compile-
1549: time error "recursive call could loop indefinitely" because pcre_compile()
1550: was not correctly checking the subroutine for matching a non-empty string.
1551:
1552: 14. The checks for overrunning compiling workspace could trigger after an
1553: overrun had occurred. This is a "should never occur" error, but it can be
1554: triggered by pathological patterns such as hundreds of nested parentheses.
1555: The checks now trigger 100 bytes before the end of the workspace.
1556:
1557: 15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1558:
1559:
1560: Version 8.01 19-Jan-2010
1561: ------------------------
1562:
1563: 1. If a pattern contained a conditional subpattern with only one branch (in
1564: particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1565: computed the wrong minimum data length (which is of course zero for such
1566: subpatterns). This could cause incorrect "no match" results.
1567:
1568: 2. For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1569: the pattern is reset in the first branch, pcre_compile() failed with
1570: "internal error: code overflow at offset...". This happened only when
1571: the reset was to the original external option setting. (An optimization
1572: abstracts leading options settings into an external setting, which was the
1573: cause of this.)
1574:
1575: 3. A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1576: of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1577: assertion pattern did not match (meaning that the assertion was true), it
1578: was incorrectly treated as false if the SKIP had been reached during the
1579: matching. This also applied to assertions used as conditions.
1580:
1581: 4. If an item that is not supported by pcre_dfa_exec() was encountered in an
1582: assertion subpattern, including such a pattern used as a condition,
1583: unpredictable results occurred, instead of the error return
1584: PCRE_ERROR_DFA_UITEM.
1585:
1586: 5. The C++ GlobalReplace function was not working like Perl for the special
1587: situation when an empty string is matched. It now does the fancy magic
1588: stuff that is necessary.
1589:
1590: 6. In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1591: removed. (These were left over from very, very early versions of PCRE.)
1592:
1593: 7. Some cosmetic changes to the code to make life easier when compiling it
1594: as part of something else:
1595:
1596: (a) Change DEBUG to PCRE_DEBUG.
1597:
1598: (b) In pcre_compile(), rename the member of the "branch_chain" structure
1599: called "current" as "current_branch", to prevent a collision with the
1600: Linux macro when compiled as a kernel module.
1601:
1602: (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1603: prevent a collision with the Linux macro when compiled as a kernel
1604: module.
1605:
1606: 8. In pcre_compile() there are some checks for integer overflows that used to
1607: cast potentially large values to (double). This has been changed to that
1608: when building, a check for int64_t is made, and if it is found, it is used
1609: instead, thus avoiding the use of floating point arithmetic. (There is no
1610: other use of FP in PCRE.) If int64_t is not found, the fallback is to
1611: double.
1612:
1613: 9. Added two casts to avoid signed/unsigned warnings from VS Studio Express
1614: 2005 (difference between two addresses compared to an unsigned value).
1615:
1616: 10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1617: custom one, because of the following reported problem in Windows:
1618:
1619: - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1620: under Win32.
1621: - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1622: therefore missing the function definition.
1623: - The compiler thus generates a "C" signature for the test function.
1624: - The linker fails to find the "C" function.
1625: - PCRE fails to configure if asked to do so against libbz2.
1626:
1627: 11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1628: messages were output:
1629:
1630: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1631: rerunning libtoolize, to keep the correct libtool macros in-tree.
1632: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1633:
1634: I have done both of these things.
1635:
1636: 12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1637: most of the time, it *can* run out if it is given a pattern that contains a
1638: runaway infinite recursion. I updated the discussion in the pcrestack man
1639: page.
1640:
1641: 13. Now that we have gone to the x.xx style of version numbers, the minor
1642: version may start with zero. Using 08 or 09 is a bad idea because users
1643: might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1644: interpreted as invalid octal numbers. I've updated the previous comment in
1645: configure.ac, and also added a check that gives an error if 08 or 09 are
1646: used.
1647:
1648: 14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1649: causing partial matching to fail when the end of the subject matched \W
1650: in a UTF-8 pattern where \W was quantified with a minimum of 3.
1651:
1652: 15. There were some discrepancies between the declarations in pcre_internal.h
1653: of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1654: their definitions. The declarations used "const uschar *" and the
1655: definitions used USPTR. Even though USPTR is normally defined as "const
1656: unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1657: reported that: "This difference in casting confuses some C++ compilers, for
1658: example, SunCC recognizes above declarations as different functions and
1659: generates broken code for hbpcre." I have changed the declarations to use
1660: USPTR.
1661:
1662: 16. GNU libtool is named differently on some systems. The autogen.sh script now
1663: tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1664: (FreeBSD).
1665:
1666: 17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1667: (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1668: comment: "Figure out how to create a longlong from a string: strtoll and
1669: equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1670: instance, but it only takes 2 args instead of 3!"
1671:
1672: 18. A subtle bug concerned with back references has been fixed by a change of
1673: specification, with a corresponding code fix. A pattern such as
1674: ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1675: refers, was giving matches when it shouldn't. For example, xa=xaaa would
1676: match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1677: same bug. Such groups have to be quantified to be useful, or contained
1678: inside another quantified group. (If there's no repetition, the reference
1679: can never match.) The problem arises because, having left the group and
1680: moved on to the rest of the pattern, a later failure that backtracks into
1681: the group uses the captured value from the final iteration of the group
1682: rather than the correct earlier one. I have fixed this in PCRE by forcing
1683: any group that contains a reference to itself to be an atomic group; that
1684: is, there cannot be any backtracking into it once it has completed. This is
1685: similar to recursive and subroutine calls.
1686:
1687:
1688: Version 8.00 19-Oct-09
1689: ----------------------
1690:
1691: 1. The table for translating pcre_compile() error codes into POSIX error codes
1692: was out-of-date, and there was no check on the pcre_compile() error code
1693: being within the table. This could lead to an OK return being given in
1694: error.
1695:
1696: 2. Changed the call to open a subject file in pcregrep from fopen(pathname,
1697: "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1698: in a Windows environment.
1699:
1700: 3. The pcregrep --count option prints the count for each file even when it is
1701: zero, as does GNU grep. However, pcregrep was also printing all files when
1702: --files-with-matches was added. Now, when both options are given, it prints
1703: counts only for those files that have at least one match. (GNU grep just
1704: prints the file name in this circumstance, but including the count seems
1705: more useful - otherwise, why use --count?) Also ensured that the
1706: combination -clh just lists non-zero counts, with no names.
1707:
1708: 4. The long form of the pcregrep -F option was incorrectly implemented as
1709: --fixed_strings instead of --fixed-strings. This is an incompatible change,
1710: but it seems right to fix it, and I didn't think it was worth preserving
1711: the old behaviour.
1712:
1713: 5. The command line items --regex=pattern and --regexp=pattern were not
1714: recognized by pcregrep, which required --regex pattern or --regexp pattern
1715: (with a space rather than an '='). The man page documented the '=' forms,
1716: which are compatible with GNU grep; these now work.
1717:
1718: 6. No libpcreposix.pc file was created for pkg-config; there was just
1719: libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1720:
1721: 7. Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1722: when UCP support is not needed, by modifying the Python script that
1723: generates it from Unicode data files. This should not matter if the module
1724: is correctly used as a library, but I received one complaint about 50K of
1725: unwanted data. My guess is that the person linked everything into his
1726: program rather than using a library. Anyway, it does no harm.
1727:
1728: 8. A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1729: was a minimum greater than 1 for a wide character in a possessive
1730: repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1731: which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1732: character. Chaos in the form of incorrect output or a compiling loop could
1733: result.
1734:
1735: 9. The restrictions on what a pattern can contain when partial matching is
1736: requested for pcre_exec() have been removed. All patterns can now be
1737: partially matched by this function. In addition, if there are at least two
1738: slots in the offset vector, the offset of the earliest inspected character
1739: for the match and the offset of the end of the subject are set in them when
1740: PCRE_ERROR_PARTIAL is returned.
1741:
1742: 10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1743: synonymous with PCRE_PARTIAL, for backwards compatibility, and
1744: PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1745: and may be more useful for multi-segment matching.
1746:
1747: 11. Partial matching with pcre_exec() is now more intuitive. A partial match
1748: used to be given if ever the end of the subject was reached; now it is
1749: given only if matching could not proceed because another character was
1750: needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1751: string "Z", which now yields "no match" instead of "partial match". In the
1752: case of pcre_dfa_exec(), "no match" is given if every matching path for the
1753: final character ended with (*FAIL).
1754:
1755: 12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1756: if the pattern had a "must contain" character that was already found in the
1757: earlier partial match, unless partial matching was again requested. For
1758: example, with the pattern /dog.(body)?/, the "must contain" character is
1759: "g". If the first part-match was for the string "dog", restarting with
1760: "sbody" failed. This bug has been fixed.
1761:
1762: 13. The string returned by pcre_dfa_exec() after a partial match has been
1763: changed so that it starts at the first inspected character rather than the
1764: first character of the match. This makes a difference only if the pattern
1765: starts with a lookbehind assertion or \b or \B (\K is not supported by
1766: pcre_dfa_exec()). It's an incompatible change, but it makes the two
1767: matching functions compatible, and I think it's the right thing to do.
1768:
1769: 14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1770: so that the demonstration program is easily available in environments where
1771: PCRE has not been installed from source.
1772:
1773: 15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1774: libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1775: library.
1776:
1777: 16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1778: It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1779: is not the first non-POSIX option to be added. Clearly some people find
1780: these options useful.
1781:
1782: 17. If a caller to the POSIX matching function regexec() passes a non-zero
1783: value for nmatch with a NULL value for pmatch, the value of
1784: nmatch is forced to zero.
1785:
1786: 18. RunGrepTest did not have a test for the availability of the -u option of
1787: the diff command, as RunTest does. It now checks in the same way as
1788: RunTest, and also checks for the -b option.
1789:
1790: 19. If an odd number of negated classes containing just a single character
1791: interposed, within parentheses, between a forward reference to a named
1792: subpattern and the definition of the subpattern, compilation crashed with
1793: an internal error, complaining that it could not find the referenced
1794: subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1795: [The bug was that it was starting one character too far in when skipping
1796: over the character class, thus treating the ] as data rather than
1797: terminating the class. This meant it could skip too much.]
1798:
1799: 20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1800: /g option in pcretest when the pattern contains \K, which makes it possible
1801: to have an empty string match not at the start, even when the pattern is
1802: anchored. Updated pcretest and pcredemo to use this option.
1803:
1804: 21. If the maximum number of capturing subpatterns in a recursion was greater
1805: than the maximum at the outer level, the higher number was returned, but
1806: with unset values at the outer level. The correct (outer level) value is
1807: now given.
1808:
1809: 22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1810: PCRE did not set those parentheses (unlike Perl). I have now found a way to
1811: make it do so. The string so far is captured, making this feature
1812: compatible with Perl.
1813:
1814: 23. The tests have been re-organized, adding tests 11 and 12, to make it
1815: possible to check the Perl 5.10 features against Perl 5.10.
1816:
1817: 24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1818: pattern matches a fixed length string. PCRE did not allow this; now it
1819: does. Neither allows recursion.
1820:
1821: 25. I finally figured out how to implement a request to provide the minimum
1822: length of subject string that was needed in order to match a given pattern.
1823: (It was back references and recursion that I had previously got hung up
1824: on.) This code has now been added to pcre_study(); it finds a lower bound
1825: to the length of subject needed. It is not necessarily the greatest lower
1826: bound, but using it to avoid searching strings that are too short does give
1827: some useful speed-ups. The value is available to calling programs via
1828: pcre_fullinfo().
1829:
1830: 26. While implementing 25, I discovered to my embarrassment that pcretest had
1831: not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1832: study optimizations had never been tested with that matching function.
1833: Oops. What is worse, even when it was passed study data, there was a bug in
1834: pcre_dfa_exec() that meant it never actually used it. Double oops. There
1835: were also very few tests of studied patterns with pcre_dfa_exec().
1836:
1837: 27. If (?| is used to create subpatterns with duplicate numbers, they are now
1838: allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1839: on the other side of the coin, they are no longer allowed to have different
1840: names, because these cannot be distinguished in PCRE, and this has caused
1841: confusion. (This is a difference from Perl.)
1842:
1843: 28. When duplicate subpattern names are present (necessarily with different
1844: numbers, as required by 27 above), and a test is made by name in a
1845: conditional pattern, either for a subpattern having been matched, or for
1846: recursion in such a pattern, all the associated numbered subpatterns are
1847: tested, and the overall condition is true if the condition is true for any
1848: one of them. This is the way Perl works, and is also more like the way
1849: testing by number works.
1850:
1851:
1852: Version 7.9 11-Apr-09
1853: ---------------------
1854:
1855: 1. When building with support for bzlib/zlib (pcregrep) and/or readline
1856: (pcretest), all targets were linked against these libraries. This included
1857: libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1858: libraries. This caused unwanted dependencies to be created. This problem
1859: has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1860: pcretest is linked with readline.
1861:
1862: 2. The "typedef int BOOL" in pcre_internal.h that was included inside the
1863: "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1864: moved outside it again, because FALSE and TRUE are already defined in AIX,
1865: but BOOL is not.
1866:
1867: 3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1868: PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1869:
1870: 4. The pcregrep documentation said spaces were inserted as well as colons (or
1871: hyphens) following file names and line numbers when outputting matching
1872: lines. This is not true; no spaces are inserted. I have also clarified the
1873: wording for the --colour (or --color) option.
1874:
1875: 5. In pcregrep, when --colour was used with -o, the list of matching strings
1876: was not coloured; this is different to GNU grep, so I have changed it to be
1877: the same.
1878:
1879: 6. When --colo(u)r was used in pcregrep, only the first matching substring in
1880: each matching line was coloured. Now it goes on to look for further matches
1881: of any of the test patterns, which is the same behaviour as GNU grep.
1882:
1883: 7. A pattern that could match an empty string could cause pcregrep to loop; it
1884: doesn't make sense to accept an empty string match in pcregrep, so I have
1885: locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1.1.1.4 misho 1886: seems to be how GNU grep behaves. [But see later change 40 for release
1887: 8.33.]
1.1 misho 1888:
1889: 8. The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1890: start or after a newline", because the conditional assertion was not being
1891: correctly handled. The rule now is that both the assertion and what follows
1892: in the first alternative must satisfy the test.
1893:
1894: 9. If auto-callout was enabled in a pattern with a conditional group whose
1895: condition was an assertion, PCRE could crash during matching, both with
1896: pcre_exec() and pcre_dfa_exec().
1897:
1898: 10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1899: used for matching.
1900:
1901: 11. Unicode property support in character classes was not working for
1902: characters (bytes) greater than 127 when not in UTF-8 mode.
1903:
1904: 12. Added the -M command line option to pcretest.
1905:
1906: 14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1907:
1908: 15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1909:
1910: 16. Added comments and documentation about mis-use of no_arg in the C++
1911: wrapper.
1912:
1913: 17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1914: from Martin Jerabek that uses macro names for all relevant character and
1915: string constants.
1916:
1917: 18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1918: SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1919: SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1920: these, but not everybody uses configure.
1921:
1922: 19. A conditional group that had only one branch was not being correctly
1923: recognized as an item that could match an empty string. This meant that an
1924: enclosing group might also not be so recognized, causing infinite looping
1925: (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1926: with the subject "ab", where knowledge that the repeated group can match
1927: nothing is needed in order to break the loop.
1928:
1929: 20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1930: exec(), but without supplying a callout function, matching went wrong.
1931:
1932: 21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1933: leak if the size of the offset vector was greater than 30. When the vector
1934: is smaller, the saved offsets during recursion go onto a local stack
1935: vector, but for larger vectors malloc() is used. It was failing to free
1936: when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1937: error, in fact).
1938:
1939: 22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1940: heapframe that is used only when UTF-8 support is enabled. This caused no
1941: problem, but was untidy.
1942:
1943: 23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1944: CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1945: included within another project.
1946:
1947: 24. Steven Van Ingelgem's patches to add more options to the CMake support,
1948: slightly modified by me:
1949:
1950: (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1951: not building pcregrep.
1952:
1953: (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1954: if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1955:
1956: 25. Forward references, both numeric and by name, in patterns that made use of
1957: duplicate group numbers, could behave incorrectly or give incorrect errors,
1958: because when scanning forward to find the reference group, PCRE was not
1959: taking into account the duplicate group numbers. A pattern such as
1960: ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1961:
1962: 26. Changed a few more instances of "const unsigned char *" to USPTR, making
1963: the feature of a custom pointer more persuasive (as requested by a user).
1964:
1965: 27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1966: pcretest.c, inside #ifndefs, because it seems they are sometimes already
1967: pre-defined.
1968:
1969: 28. Added support for (*UTF8) at the start of a pattern.
1970:
1971: 29. Arrange for flags added by the "release type" setting in CMake to be shown
1972: in the configuration summary.
1973:
1974:
1975: Version 7.8 05-Sep-08
1976: ---------------------
1977:
1978: 1. Replaced UCP searching code with optimized version as implemented for Ad
1979: Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1980: stage table and inline lookup instead of a function, giving speed ups of 2
1981: to 5 times on some simple patterns that I tested. Permission was given to
1982: distribute the MultiStage2.py script that generates the tables (it's not in
1983: the tarball, but is in the Subversion repository).
1984:
1985: 2. Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1986: scripts.
1987:
1988: 3. Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1989: a group with a zero qualifier. The result of the study could be incorrect,
1990: or the function might crash, depending on the pattern.
1991:
1992: 4. Caseless matching was not working for non-ASCII characters in back
1993: references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1994: It now works when Unicode Property Support is available.
1995:
1996: 5. In pcretest, an escape such as \x{de} in the data was always generating
1997: a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1998: non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1999: truncation.
2000:
2001: 6. Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
2002:
2003: 7. Added two (int) casts to pcregrep when printing the difference of two
2004: pointers, in case they are 64-bit values.
2005:
2006: 8. Added comments about Mac OS X stack usage to the pcrestack man page and to
2007: test 2 if it fails.
2008:
2009: 9. Added PCRE_CALL_CONVENTION just before the names of all exported functions,
2010: and a #define of that name to empty if it is not externally set. This is to
2011: allow users of MSVC to set it if necessary.
2012:
2013: 10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
2014: the convenience functions in the pcre_get.c source file.
2015:
2016: 11. An option change at the start of a pattern that had top-level alternatives
2017: could cause overwriting and/or a crash. This command provoked a crash in
2018: some environments:
2019:
2020: printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
2021:
2022: This potential security problem was recorded as CVE-2008-2371.
2023:
2024: 12. For a pattern where the match had to start at the beginning or immediately
2025: after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
2026: pcre_dfa_exec() could read past the end of the passed subject if there was
2027: no match. To help with detecting such bugs (e.g. with valgrind), I modified
2028: pcretest so that it places the subject at the end of its malloc-ed buffer.
2029:
2030: 13. The change to pcretest in 12 above threw up a couple more cases when pcre_
2031: exec() might read past the end of the data buffer in UTF-8 mode.
2032:
2033: 14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
2034: the data contained the byte 0x85 as part of a UTF-8 character within its
2035: first line. This applied both to normal and DFA matching.
2036:
2037: 15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
2038: /^[^d]*?$/8 failed to match "abc".
2039:
2040: 16. Added a missing copyright notice to pcrecpp_internal.h.
2041:
2042: 17. Make it more clear in the documentation that values returned from
2043: pcre_exec() in ovector are byte offsets, not character counts.
2044:
2045: 18. Tidied a few places to stop certain compilers from issuing warnings.
2046:
2047: 19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
2048: supplied by Stefan Weber. I made a further small update for 7.8 because
2049: there is a change of source arrangements: the pcre_searchfuncs.c module is
2050: replaced by pcre_ucd.c.
2051:
2052:
2053: Version 7.7 07-May-08
2054: ---------------------
2055:
2056: 1. Applied Craig's patch to sort out a long long problem: "If we can't convert
2057: a string to a long long, pretend we don't even have a long long." This is
2058: done by checking for the strtoq, strtoll, and _strtoi64 functions.
2059:
2060: 2. Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
2061: pre-7.6 versions, which defined a global no_arg variable instead of putting
2062: it in the RE class. (See also #8 below.)
2063:
2064: 3. Remove a line of dead code, identified by coverity and reported by Nuno
2065: Lopes.
2066:
2067: 4. Fixed two related pcregrep bugs involving -r with --include or --exclude:
2068:
2069: (1) The include/exclude patterns were being applied to the whole pathnames
2070: of files, instead of just to the final components.
2071:
2072: (2) If there was more than one level of directory, the subdirectories were
2073: skipped unless they satisfied the include/exclude conditions. This is
2074: inconsistent with GNU grep (and could even be seen as contrary to the
2075: pcregrep specification - which I improved to make it absolutely clear).
2076: The action now is always to scan all levels of directory, and just
2077: apply the include/exclude patterns to regular files.
2078:
2079: 5. Added the --include_dir and --exclude_dir patterns to pcregrep, and used
2080: --exclude_dir in the tests to avoid scanning .svn directories.
2081:
2082: 6. Applied Craig's patch to the QuoteMeta function so that it escapes the
2083: NUL character as backslash + 0 rather than backslash + NUL, because PCRE
2084: doesn't support NULs in patterns.
2085:
2086: 7. Added some missing "const"s to declarations of static tables in
2087: pcre_compile.c and pcre_dfa_exec.c.
2088:
2089: 8. Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
2090: caused by fix #2 above. (Subsequently also a second patch to fix the
2091: first patch. And a third patch - this was a messy problem.)
2092:
2093: 9. Applied Craig's patch to remove the use of push_back().
2094:
2095: 10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
2096: matching function regexec().
2097:
2098: 11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
2099: which, however, unlike Perl's \g{...}, are subroutine calls, not back
2100: references. PCRE supports relative numbers with this syntax (I don't think
2101: Oniguruma does).
2102:
2103: 12. Previously, a group with a zero repeat such as (...){0} was completely
2104: omitted from the compiled regex. However, this means that if the group
2105: was called as a subroutine from elsewhere in the pattern, things went wrong
2106: (an internal error was given). Such groups are now left in the compiled
2107: pattern, with a new opcode that causes them to be skipped at execution
2108: time.
2109:
2110: 13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
2111: to the way PCRE behaves:
2112:
2113: (a) A lone ] character is dis-allowed (Perl treats it as data).
2114:
2115: (b) A back reference to an unmatched subpattern matches an empty string
2116: (Perl fails the current match path).
2117:
2118: (c) A data ] in a character class must be notated as \] because if the
2119: first data character in a class is ], it defines an empty class. (In
2120: Perl it is not possible to have an empty class.) The empty class []
2121: never matches; it forces failure and is equivalent to (*FAIL) or (?!).
2122: The negative empty class [^] matches any one character, independently
2123: of the DOTALL setting.
2124:
2125: 14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
2126: non-existent subpattern following a character class starting with ']' and
2127: containing () gave an internal compiling error instead of "reference to
2128: non-existent subpattern". Fortunately, when the pattern did exist, the
2129: compiled code was correct. (When scanning forwards to check for the
1.1.1.4 misho 2130: existence of the subpattern, it was treating the data ']' as terminating
1.1 misho 2131: the class, so got the count wrong. When actually compiling, the reference
2132: was subsequently set up correctly.)
2133:
2134: 15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
2135: it was being rejected as not supported by pcre_dfa_exec(), even though
2136: other assertions are supported. I have made pcre_dfa_exec() support
2137: (*FAIL).
2138:
2139: 16. The implementation of 13c above involved the invention of a new opcode,
2140: OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
2141: cannot be changed at match time, I realized I could make a small
2142: improvement to matching performance by compiling OP_ALLANY instead of
2143: OP_ANY for "." when DOTALL was set, and then removing the runtime tests
2144: on the OP_ANY path.
2145:
2146: 17. Compiling pcretest on Windows with readline support failed without the
2147: following two fixes: (1) Make the unistd.h include conditional on
2148: HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
2149:
2150: 18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
2151: ncurses library to be included for pcretest when ReadLine support is
2152: requested, but also to allow for it to be overridden. This patch came from
2153: Daniel Bergström.
2154:
2155: 19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
2156: as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
2157: any errors with the current Unicode tables. Thanks to Peter Kankowski for
2158: spotting this.
2159:
2160:
2161: Version 7.6 28-Jan-08
2162: ---------------------
2163:
2164: 1. A character class containing a very large number of characters with
2165: codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
2166: overflow.
2167:
2168: 2. Patch to cut out the "long long" test in pcrecpp_unittest when
2169: HAVE_LONG_LONG is not defined.
2170:
2171: 3. Applied Christian Ehrlicher's patch to update the CMake build files to
2172: bring them up to date and include new features. This patch includes:
2173:
2174: - Fixed PH's badly added libz and libbz2 support.
2175: - Fixed a problem with static linking.
2176: - Added pcredemo. [But later removed - see 7 below.]
2177: - Fixed dftables problem and added an option.
2178: - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
2179: HAVE_LONG_LONG.
2180: - Added readline support for pcretest.
2181: - Added an listing of the option settings after cmake has run.
2182:
2183: 4. A user submitted a patch to Makefile that makes it easy to create
2184: "pcre.dll" under mingw when using Configure/Make. I added stuff to
2185: Makefile.am that cause it to include this special target, without
2186: affecting anything else. Note that the same mingw target plus all
2187: the other distribution libraries and programs are now supported
2188: when configuring with CMake (see 6 below) instead of with
2189: Configure/Make.
2190:
2191: 5. Applied Craig's patch that moves no_arg into the RE class in the C++ code.
2192: This is an attempt to solve the reported problem "pcrecpp::no_arg is not
2193: exported in the Windows port". It has not yet been confirmed that the patch
2194: solves the problem, but it does no harm.
2195:
2196: 6. Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
2197: NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
2198: with CMake, and also correct the comment about stack recursion.
2199:
2200: 7. Remove the automatic building of pcredemo from the ./configure system and
2201: from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
2202: of a program that users should build themselves after PCRE is installed, so
2203: building it automatically is not really right. What is more, it gave
2204: trouble in some build environments.
2205:
2206: 8. Further tidies to CMakeLists.txt from Sheri and Christian.
2207:
2208:
2209: Version 7.5 10-Jan-08
2210: ---------------------
2211:
2212: 1. Applied a patch from Craig: "This patch makes it possible to 'ignore'
2213: values in parens when parsing an RE using the C++ wrapper."
2214:
2215: 2. Negative specials like \S did not work in character classes in UTF-8 mode.
2216: Characters greater than 255 were excluded from the class instead of being
2217: included.
2218:
2219: 3. The same bug as (2) above applied to negated POSIX classes such as
2220: [:^space:].
2221:
2222: 4. PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
2223: defined or documented. It seems to have been a typo for PCRE_STATIC, so
2224: I have changed it.
2225:
2226: 5. The construct (?&) was not diagnosed as a syntax error (it referenced the
2227: first named subpattern) and a construct such as (?&a) would reference the
2228: first named subpattern whose name started with "a" (in other words, the
2229: length check was missing). Both these problems are fixed. "Subpattern name
2230: expected" is now given for (?&) (a zero-length name), and this patch also
2231: makes it give the same error for \k'' (previously it complained that that
2232: was a reference to a non-existent subpattern).
2233:
2234: 6. The erroneous patterns (?+-a) and (?-+a) give different error messages;
2235: this is right because (?- can be followed by option settings as well as by
2236: digits. I have, however, made the messages clearer.
2237:
2238: 7. Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
2239: than the number used in the conditional) now cause a compile-time error.
2240: This is actually not compatible with Perl, which accepts such patterns, but
2241: treats the conditional as always being FALSE (as PCRE used to), but it
2242: seems to me that giving a diagnostic is better.
2243:
2244: 8. Change "alphameric" to the more common word "alphanumeric" in comments
2245: and messages.
2246:
2247: 9. Fix two occurrences of "backslash" in comments that should have been
2248: "backspace".
2249:
2250: 10. Remove two redundant lines of code that can never be obeyed (their function
2251: was moved elsewhere).
2252:
2253: 11. The program that makes PCRE's Unicode character property table had a bug
2254: which caused it to generate incorrect table entries for sequences of
2255: characters that have the same character type, but are in different scripts.
2256: It amalgamated them into a single range, with the script of the first of
2257: them. In other words, some characters were in the wrong script. There were
2258: thirteen such cases, affecting characters in the following ranges:
2259:
2260: U+002b0 - U+002c1
2261: U+0060c - U+0060d
2262: U+0061e - U+00612
2263: U+0064b - U+0065e
2264: U+0074d - U+0076d
2265: U+01800 - U+01805
2266: U+01d00 - U+01d77
2267: U+01d9b - U+01dbf
2268: U+0200b - U+0200f
2269: U+030fc - U+030fe
2270: U+03260 - U+0327f
2271: U+0fb46 - U+0fbb1
2272: U+10450 - U+1049d
2273:
2274: 12. The -o option (show only the matching part of a line) for pcregrep was not
2275: compatible with GNU grep in that, if there was more than one match in a
2276: line, it showed only the first of them. It now behaves in the same way as
2277: GNU grep.
2278:
2279: 13. If the -o and -v options were combined for pcregrep, it printed a blank
2280: line for every non-matching line. GNU grep prints nothing, and pcregrep now
2281: does the same. The return code can be used to tell if there were any
2282: non-matching lines.
2283:
2284: 14. Added --file-offsets and --line-offsets to pcregrep.
2285:
2286: 15. The pattern (?=something)(?R) was not being diagnosed as a potentially
2287: infinitely looping recursion. The bug was that positive lookaheads were not
2288: being skipped when checking for a possible empty match (negative lookaheads
2289: and both kinds of lookbehind were skipped).
2290:
2291: 16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
2292: inclusion of <windows.h> to before rather than after the definition of
2293: INVALID_FILE_ATTRIBUTES (patch from David Byron).
2294:
2295: 17. Specifying a possessive quantifier with a specific limit for a Unicode
2296: character property caused pcre_compile() to compile bad code, which led at
2297: runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
2298: are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
2299: caused the error; without that there was no problem.
2300:
2301: 18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
2302:
2303: 19. Added --enable-pcretest-libreadline.
2304:
2305: 20. In pcrecpp.cc, the variable 'count' was incremented twice in
2306: RE::GlobalReplace(). As a result, the number of replacements returned was
2307: double what it should be. I removed one of the increments, but Craig sent a
2308: later patch that removed the other one (the right fix) and added unit tests
2309: that check the return values (which was not done before).
2310:
2311: 21. Several CMake things:
2312:
2313: (1) Arranged that, when cmake is used on Unix, the libraries end up with
2314: the names libpcre and libpcreposix, not just pcre and pcreposix.
2315:
2316: (2) The above change means that pcretest and pcregrep are now correctly
2317: linked with the newly-built libraries, not previously installed ones.
2318:
2319: (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
2320:
2321: 22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
2322: crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
2323: UTF-8 newline character). The key issue is that the pattern starts .*;
2324: this means that the match must be either at the beginning, or after a
2325: newline. The bug was in the code for advancing after a failed match and
2326: checking that the new position followed a newline. It was not taking
2327: account of UTF-8 characters correctly.
2328:
2329: 23. PCRE was behaving differently from Perl in the way it recognized POSIX
2330: character classes. PCRE was not treating the sequence [:...:] as a
2331: character class unless the ... were all letters. Perl, however, seems to
2332: allow any characters between [: and :], though of course it rejects as
2333: unknown any "names" that contain non-letters, because all the known class
2334: names consist only of letters. Thus, Perl gives an error for [[:1234:]],
2335: for example, whereas PCRE did not - it did not recognize a POSIX character
2336: class. This seemed a bit dangerous, so the code has been changed to be
2337: closer to Perl. The behaviour is not identical to Perl, because PCRE will
2338: diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
2339: treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
2340: Perl does, and where it didn't before.
2341:
2342: 24. Rewrite so as to remove the single use of %n from pcregrep because in some
2343: Windows environments %n is disabled by default.
2344:
2345:
2346: Version 7.4 21-Sep-07
2347: ---------------------
2348:
2349: 1. Change 7.3/28 was implemented for classes by looking at the bitmap. This
2350: means that a class such as [\s] counted as "explicit reference to CR or
2351: LF". That isn't really right - the whole point of the change was to try to
2352: help when there was an actual mention of one of the two characters. So now
2353: the change happens only if \r or \n (or a literal CR or LF) character is
2354: encountered.
2355:
2356: 2. The 32-bit options word was also used for 6 internal flags, but the numbers
2357: of both had grown to the point where there were only 3 bits left.
2358: Fortunately, there was spare space in the data structure, and so I have
2359: moved the internal flags into a new 16-bit field to free up more option
2360: bits.
2361:
2362: 3. The appearance of (?J) at the start of a pattern set the DUPNAMES option,
2363: but did not set the internal JCHANGED flag - either of these is enough to
2364: control the way the "get" function works - but the PCRE_INFO_JCHANGED
2365: facility is supposed to tell if (?J) was ever used, so now (?J) at the
2366: start sets both bits.
2367:
2368: 4. Added options (at build time, compile time, exec time) to change \R from
2369: matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
2370:
2371: 5. doc/pcresyntax.html was missing from the distribution.
2372:
2373: 6. Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
2374: compatibility, even though it is no longer used.
2375:
2376: 7. Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
2377: strtoull to pcrecpp.cc to select the available functions in WIN32 when the
2378: windows.h file is present (where different names are used). [This was
2379: reversed later after testing - see 16 below.]
2380:
2381: 8. Changed all #include <config.h> to #include "config.h". There were also
2382: some further <pcre.h> cases that I changed to "pcre.h".
2383:
2384: 9. When pcregrep was used with the --colour option, it missed the line ending
2385: sequence off the lines that it output.
2386:
2387: 10. It was pointed out to me that arrays of string pointers cause lots of
2388: relocations when a shared library is dynamically loaded. A technique of
2389: using a single long string with a table of offsets can drastically reduce
2390: these. I have refactored PCRE in four places to do this. The result is
2391: dramatic:
2392:
2393: Originally: 290
2394: After changing UCP table: 187
2395: After changing error message table: 43
2396: After changing table of "verbs" 36
2397: After changing table of Posix names 22
2398:
2399: Thanks to the folks working on Gregex for glib for this insight.
2400:
2401: 11. --disable-stack-for-recursion caused compiling to fail unless -enable-
2402: unicode-properties was also set.
2403:
2404: 12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
2405:
2406: 13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
2407: checked only for CRLF.
2408:
2409: 14. Added casts to pcretest.c to avoid compiler warnings.
2410:
2411: 15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
2412:
2413: 16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
2414: and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
2415: entirely. This removes changes made in 7 above.
2416:
2417: 17. The CMake files have been updated, and there is now more information about
2418: building with CMake in the NON-UNIX-USE document.
2419:
2420:
2421: Version 7.3 28-Aug-07
2422: ---------------------
2423:
2424: 1. In the rejigging of the build system that eventually resulted in 7.1, the
2425: line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
2426: brackets there is not right, since it causes compilers to look for an
2427: installed pcre.h, not the version that is in the source that is being
2428: compiled (which of course may be different). I have changed it back to:
2429:
2430: #include "pcre.h"
2431:
2432: I have a vague recollection that the change was concerned with compiling in
2433: different directories, but in the new build system, that is taken care of
2434: by the VPATH setting the Makefile.
2435:
2436: 2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
2437: when the subject happened to end in the byte 0x85 (e.g. if the last
2438: character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
2439: characters but of course it shouldn't be taken as a newline when it is part
2440: of another character. The bug was that, for an unlimited repeat of . in
2441: not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
2442: characters when looking for a newline.
2443:
2444: 3. A small performance improvement in the DOTALL UTF-8 mode .* case.
2445:
2446: 4. Debugging: adjusted the names of opcodes for different kinds of parentheses
2447: in debug output.
2448:
2449: 5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
2450: long printing in the pcrecpp unittest when running under MinGW.
2451:
2452: 6. ESC_K was left out of the EBCDIC table.
2453:
2454: 7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
2455: parentheses; I made it 1000, which seemed large enough. Unfortunately, the
2456: limit also applies to "virtual nesting" when a pattern is recursive, and in
2457: this case 1000 isn't so big. I have been able to remove this limit at the
2458: expense of backing off one optimization in certain circumstances. Normally,
2459: when pcre_exec() would call its internal match() function recursively and
2460: immediately return the result unconditionally, it uses a "tail recursion"
2461: feature to save stack. However, when a subpattern that can match an empty
2462: string has an unlimited repetition quantifier, it no longer makes this
2463: optimization. That gives it a stack frame in which to save the data for
2464: checking that an empty string has been matched. Previously this was taken
2465: from the 1000-entry workspace that had been reserved. So now there is no
2466: explicit limit, but more stack is used.
2467:
2468: 8. Applied Daniel's patches to solve problems with the import/export magic
2469: syntax that is required for Windows, and which was going wrong for the
2470: pcreposix and pcrecpp parts of the library. These were overlooked when this
2471: problem was solved for the main library.
2472:
2473: 9. There were some crude static tests to avoid integer overflow when computing
2474: the size of patterns that contain repeated groups with explicit upper
2475: limits. As the maximum quantifier is 65535, the maximum group length was
2476: set at 30,000 so that the product of these two numbers did not overflow a
2477: 32-bit integer. However, it turns out that people want to use groups that
2478: are longer than 30,000 bytes (though not repeat them that many times).
2479: Change 7.0/17 (the refactoring of the way the pattern size is computed) has
2480: made it possible to implement the integer overflow checks in a much more
2481: dynamic way, which I have now done. The artificial limitation on group
2482: length has been removed - we now have only the limit on the total length of
2483: the compiled pattern, which depends on the LINK_SIZE setting.
2484:
2485: 10. Fixed a bug in the documentation for get/copy named substring when
2486: duplicate names are permitted. If none of the named substrings are set, the
2487: functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
2488: empty string.
2489:
2490: 11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
2491: instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
2492: because the ] is interpreted as the first data character and the
2493: terminating ] is not found. PCRE has been made compatible with Perl in this
2494: regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
2495: cause memory overwriting.
2496:
2497: 10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
2498: string has been matched (to stop an infinite loop). It was not recognizing
2499: a conditional subpattern that could match an empty string if that
2500: subpattern was within another subpattern. For example, it looped when
2501: trying to match (((?(1)X|))*) but it was OK with ((?(1)X|)*) where the
2502: condition was not nested. This bug has been fixed.
2503:
2504: 12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
2505: past the start of the subject in the presence of bytes with the top bit
2506: set, for example "\x8aBCD".
2507:
2508: 13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
2509: (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
2510:
2511: 14. Optimized (?!) to (*FAIL).
2512:
2513: 15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
2514: This restricts code points to be within the range 0 to 0x10FFFF, excluding
2515: the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
2516: full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
2517: does: it's just the validity check that is more restrictive.
2518:
2519: 16. Inserted checks for integer overflows during escape sequence (backslash)
2520: processing, and also fixed erroneous offset values for syntax errors during
2521: backslash processing.
2522:
2523: 17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
2524: for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
2525:
2526: 18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
2527: caused an overrun.
2528:
2529: 19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
2530: something other than just ASCII characters) inside a group that had an
2531: unlimited repeat caused a loop at compile time (while checking to see
2532: whether the group could match an empty string).
2533:
2534: 20. Debugging a pattern containing \p or \P could cause a crash. For example,
2535: [\P{Any}] did so. (Error in the code for printing property names.)
2536:
2537: 21. An orphan \E inside a character class could cause a crash.
2538:
2539: 22. A repeated capturing bracket such as (A)? could cause a wild memory
2540: reference during compilation.
2541:
2542: 23. There are several functions in pcre_compile() that scan along a compiled
2543: expression for various reasons (e.g. to see if it's fixed length for look
2544: behind). There were bugs in these functions when a repeated \p or \P was
2545: present in the pattern. These operators have additional parameters compared
2546: with \d, etc, and these were not being taken into account when moving along
2547: the compiled data. Specifically:
2548:
2549: (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
2550: length.
2551:
2552: (b) An item such as \pL+ within a repeated group could cause crashes or
2553: loops.
2554:
2555: (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
2556: "reference to non-existent subpattern" error.
2557:
2558: (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
2559:
2560: 24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
2561: characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
2562:
2563: 25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
2564:
2565: 26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
2566: character were causing crashes (broken optimization).
2567:
2568: 27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2569: \p or \P) caused a compile-time loop.
2570:
2571: 28. More problems have arisen in unanchored patterns when CRLF is a valid line
2572: break. For example, the unstudied pattern [\r\n]A does not match the string
2573: "\r\nA" because change 7.0/46 below moves the current point on by two
2574: characters after failing to match at the start. However, the pattern \nA
2575: *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2576: the same is true. There doesn't seem any very clean way out of this, but
2577: what I have chosen to do makes the common cases work: PCRE now takes note
2578: of whether there can be an explicit match for \r or \n anywhere in the
2579: pattern, and if so, 7.0/46 no longer applies. As part of this change,
2580: there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2581: pattern has explicit CR or LF references.
2582:
2583: 29. Added (*CR) etc for changing newline setting at start of pattern.
2584:
2585:
2586: Version 7.2 19-Jun-07
2587: ---------------------
2588:
2589: 1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
2590: which is apparently normally available under Windows.
2591:
2592: 2. Re-jig the pcregrep tests with different newline settings in an attempt
2593: to make them independent of the local environment's newline setting.
2594:
2595: 3. Add code to configure.ac to remove -g from the CFLAGS default settings.
2596:
2597: 4. Some of the "internals" tests were previously cut out when the link size
2598: was not 2, because the output contained actual offsets. The recent new
2599: "Z" feature of pcretest means that these can be cut out, making the tests
2600: usable with all link sizes.
2601:
2602: 5. Implemented Stan Switzer's goto replacement for longjmp() when not using
2603: stack recursion. This gives a massive performance boost under BSD, but just
2604: a small improvement under Linux. However, it saves one field in the frame
2605: in all cases.
2606:
2607: 6. Added more features from the forthcoming Perl 5.10:
2608:
2609: (a) (?-n) (where n is a string of digits) is a relative subroutine or
2610: recursion call. It refers to the nth most recently opened parentheses.
2611:
2612: (b) (?+n) is also a relative subroutine call; it refers to the nth next
2613: to be opened parentheses.
2614:
2615: (c) Conditions that refer to capturing parentheses can be specified
2616: relatively, for example, (?(-2)... or (?(+3)...
2617:
2618: (d) \K resets the start of the current match so that everything before
2619: is not part of it.
2620:
2621: (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
2622:
2623: (f) \g{name} is another synonym - part of Perl 5.10's unification of
2624: reference syntax.
2625:
2626: (g) (?| introduces a group in which the numbering of parentheses in each
2627: alternative starts with the same number.
2628:
2629: (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
2630:
2631: 7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
2632: PCRE_INFO_JCHANGED.
2633:
2634: 8. A pattern such as (.*(.)?)* caused pcre_exec() to fail by either not
2635: terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
2636: for detecting groups that can match an empty string.
2637:
2638: 9. A pattern with a very large number of alternatives (more than several
2639: hundred) was running out of internal workspace during the pre-compile
2640: phase, where pcre_compile() figures out how much memory will be needed. A
2641: bit of new cunning has reduced the workspace needed for groups with
2642: alternatives. The 1000-alternative test pattern now uses 12 bytes of
2643: workspace instead of running out of the 4096 that are available.
2644:
2645: 10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
2646:
2647: 11. Applied patch from Google to remove an optimization that didn't quite work.
2648: The report of the bug said:
2649:
2650: pcrecpp::RE("a*").FullMatch("aaa") matches, while
2651: pcrecpp::RE("a*?").FullMatch("aaa") does not, and
2652: pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
2653:
2654: 12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
2655: it matched the wrong number of bytes.
2656:
2657:
2658: Version 7.1 24-Apr-07
2659: ---------------------
2660:
2661: 1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
2662: that is more "standard", making use of automake and other Autotools. There
2663: is some re-arrangement of the files and adjustment of comments consequent
2664: on this.
2665:
2666: 2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
2667: for recursive directory scanning broke on some systems because the files
2668: are not scanned in any specific order and on different systems the order
2669: was different. A call to "sort" has been inserted into RunGrepTest for the
2670: approprate test as a short-term fix. In the longer term there may be an
2671: alternative.
2672:
2673: 3. I had an email from Eric Raymond about problems translating some of PCRE's
2674: man pages to HTML (despite the fact that I distribute HTML pages, some
2675: people do their own conversions for various reasons). The problems
2676: concerned the use of low-level troff macros .br and .in. I have therefore
2677: removed all such uses from the man pages (some were redundant, some could
2678: be replaced by .nf/.fi pairs). The 132html script that I use to generate
2679: HTML has been updated to handle .nf/.fi and to complain if it encounters
2680: .br or .in.
2681:
2682: 4. Updated comments in configure.ac that get placed in config.h.in and also
2683: arranged for config.h to be included in the distribution, with the name
2684: config.h.generic, for the benefit of those who have to compile without
2685: Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
2686:
2687: 5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
2688: Weber: (1) pcre_internal.h was missing some function renames; (2) updated
2689: makevp.bat for the current PCRE, using the additional files
2690: makevp_c.txt, makevp_l.txt, and pcregexp.pas.
2691:
2692: 6. A Windows user reported a minor discrepancy with test 2, which turned out
2693: to be caused by a trailing space on an input line that had got lost in his
2694: copy. The trailing space was an accident, so I've just removed it.
2695:
2696: 7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
2697: that is needed.
2698:
2699: 8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
2700: as "const" (a) because they are and (b) because it helps the PHP
2701: maintainers who have recently made a script to detect big data structures
2702: in the php code that should be moved to the .rodata section. I remembered
2703: to update Builducptable as well, so it won't revert if ucptable.h is ever
2704: re-created.
2705:
2706: 9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
2707: pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
2708: order to be able to cut out the UTF-8 tables in the latter when UTF-8
2709: support is not required. This saves 1.5-2K of code, which is important in
2710: some applications.
2711:
2712: Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
2713: so as not to refer to the tables, even though these functions will never be
2714: called when UTF-8 support is disabled. Otherwise there are problems with a
2715: shared library.
2716:
2717: 10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
2718:
2719: (a) It was defining its arguments as char * instead of void *.
2720:
2721: (b) It was assuming that all moves were upwards in memory; this was true
2722: a long time ago when I wrote it, but is no longer the case.
2723:
2724: The emulated memove() is provided for those environments that have neither
2725: memmove() nor bcopy(). I didn't think anyone used it these days, but that
2726: is clearly not the case, as these two bugs were recently reported.
2727:
2728: 11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
2729: and Detrail to create the HTML documentation, the .txt form of the man
2730: pages, and it removes trailing spaces from listed files. It also creates
2731: pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
2732: case, it wraps all the #defines with #ifndefs. This script should be run
2733: before "make dist".
2734:
2735: 12. Fixed two fairly obscure bugs concerned with quantified caseless matching
2736: with Unicode property support.
2737:
2738: (a) For a maximizing quantifier, if the two different cases of the
2739: character were of different lengths in their UTF-8 codings (there are
2740: some cases like this - I found 11), and the matching function had to
2741: back up over a mixture of the two cases, it incorrectly assumed they
2742: were both the same length.
2743:
2744: (b) When PCRE was configured to use the heap rather than the stack for
2745: recursion during matching, it was not correctly preserving the data for
2746: the other case of a UTF-8 character when checking ahead for a match
2747: while processing a minimizing repeat. If the check also involved
2748: matching a wide character, but failed, corruption could cause an
2749: erroneous result when trying to check for a repeat of the original
2750: character.
2751:
2752: 13. Some tidying changes to the testing mechanism:
2753:
2754: (a) The RunTest script now detects the internal link size and whether there
2755: is UTF-8 and UCP support by running ./pcretest -C instead of relying on
2756: values substituted by "configure". (The RunGrepTest script already did
2757: this for UTF-8.) The configure.ac script no longer substitutes the
2758: relevant variables.
2759:
2760: (b) The debugging options /B and /D in pcretest show the compiled bytecode
2761: with length and offset values. This means that the output is different
2762: for different internal link sizes. Test 2 is skipped for link sizes
2763: other than 2 because of this, bypassing the problem. Unfortunately,
2764: there was also a test in test 3 (the locale tests) that used /B and
2765: failed for link sizes other than 2. Rather than cut the whole test out,
2766: I have added a new /Z option to pcretest that replaces the length and
2767: offset values with spaces. This is now used to make test 3 independent
2768: of link size. (Test 2 will be tidied up later.)
2769:
2770: 14. If erroroffset was passed as NULL to pcre_compile, it provoked a
2771: segmentation fault instead of returning the appropriate error message.
2772:
2773: 15. In multiline mode when the newline sequence was set to "any", the pattern
2774: ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
2775: This doesn't seem right; it now treats the CRLF combination as the line
2776: ending, and so does not match in that case. It's only a pattern such as ^$
2777: that would hit this one: something like ^ABC$ would have failed after \r
2778: and then tried again after \r\n.
2779:
2780: 16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
2781: in an attempt to make files that differ only in their line terminators
2782: compare equal. This works on Linux.
2783:
2784: 17. Under certain error circumstances pcregrep might try to free random memory
2785: as it exited. This is now fixed, thanks to valgrind.
2786:
2787: 19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
2788: "abc\r\n\r\n", it found an unwanted second match after the second \r. This
2789: was because its rules for how to advance for /g after matching an empty
2790: string at the end of a line did not allow for this case. They now check for
2791: it specially.
2792:
2793: 20. pcretest is supposed to handle patterns and data of any length, by
2794: extending its buffers when necessary. It was getting this wrong when the
2795: buffer for a data line had to be extended.
2796:
2797: 21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
2798: CRLF as a newline sequence.
2799:
2800: 22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
2801: out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
2802: I have nevertheless tidied it up.
2803:
2804: 23. Added some casts to kill warnings from HP-UX ia64 compiler.
2805:
2806: 24. Added a man page for pcre-config.
2807:
2808:
2809: Version 7.0 19-Dec-06
2810: ---------------------
2811:
2812: 1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
2813: moving to gcc 4.1.1.
2814:
2815: 2. The -S option for pcretest uses setrlimit(); I had omitted to #include
2816: sys/time.h, which is documented as needed for this function. It doesn't
2817: seem to matter on Linux, but it showed up on some releases of OS X.
2818:
2819: 3. It seems that there are systems where bytes whose values are greater than
2820: 127 match isprint() in the "C" locale. The "C" locale should be the
2821: default when a C program starts up. In most systems, only ASCII printing
2822: characters match isprint(). This difference caused the output from pcretest
2823: to vary, making some of the tests fail. I have changed pcretest so that:
2824:
2825: (a) When it is outputting text in the compiled version of a pattern, bytes
2826: other than 32-126 are always shown as hex escapes.
2827:
2828: (b) When it is outputting text that is a matched part of a subject string,
2829: it does the same, unless a different locale has been set for the match
2830: (using the /L modifier). In this case, it uses isprint() to decide.
2831:
2832: 4. Fixed a major bug that caused incorrect computation of the amount of memory
2833: required for a compiled pattern when options that changed within the
2834: pattern affected the logic of the preliminary scan that determines the
2835: length. The relevant options are -x, and -i in UTF-8 mode. The result was
2836: that the computed length was too small. The symptoms of this bug were
2837: either the PCRE error "internal error: code overflow" from pcre_compile(),
2838: or a glibc crash with a message such as "pcretest: free(): invalid next
2839: size (fast)". Examples of patterns that provoked this bug (shown in
2840: pcretest format) are:
2841:
2842: /(?-x: )/x
2843: /(?x)(?-x: \s*#\s*)/
2844: /((?i)[\x{c0}])/8
2845: /(?i:[\x{c0}])/8
2846:
2847: HOWEVER: Change 17 below makes this fix obsolete as the memory computation
2848: is now done differently.
2849:
2850: 5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
2851: wrapper classes; (b) implement a new function in the C++ scanner that is
2852: more efficient than the old way of doing things because it avoids levels of
2853: recursion in the regex matching; (c) add a paragraph to the documentation
2854: for the FullMatch() function.
2855:
2856: 6. The escape sequence \n was being treated as whatever was defined as
2857: "newline". Not only was this contrary to the documentation, which states
2858: that \n is character 10 (hex 0A), but it also went horribly wrong when
2859: "newline" was defined as CRLF. This has been fixed.
2860:
2861: 7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
2862: was being set to -1 for the "end of line" case (supposedly a value that no
2863: character can have). Though this value is never used (the check for end of
2864: line is "zero bytes in current character"), it caused compiler complaints.
2865: I've changed it to 0xffffffff.
2866:
2867: 8. In pcre_version.c, the version string was being built by a sequence of
2868: C macros that, in the event of PCRE_PRERELEASE being defined as an empty
2869: string (as it is for production releases) called a macro with an empty
2870: argument. The C standard says the result of this is undefined. The gcc
2871: compiler treats it as an empty string (which was what was wanted) but it is
2872: reported that Visual C gives an error. The source has been hacked around to
2873: avoid this problem.
2874:
2875: 9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
2876: builds of pcretest, and changed the call to _setmode() to use _O_BINARY
2877: instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
2878: of them did).
2879:
2880: 10. Originally, pcretest opened its input and output without "b"; then I was
2881: told that "b" was needed in some environments, so it was added for release
2882: 5.0 to both the input and output. (It makes no difference on Unix-like
2883: systems.) Later I was told that it is wrong for the input on Windows. I've
2884: now abstracted the modes into two macros, to make it easier to fiddle with
2885: them, and removed "b" from the input mode under Windows.
2886:
2887: 11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
2888:
2889: 12. Added -help and --help to pcretest as an official way of being reminded
2890: of the options.
2891:
2892: 13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
2893: and pcrecpp.cc because they annoy compilers at high warning levels.
2894:
2895: 14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
2896:
2897: 15. Fixed an occurrence of == in configure.ac that should have been = (shell
2898: scripts are not C programs :-) and which was not noticed because it works
2899: on Linux.
2900:
2901: 16. pcretest is supposed to handle any length of pattern and data line (as one
2902: line or as a continued sequence of lines) by extending its input buffer if
2903: necessary. This feature was broken for very long pattern lines, leading to
2904: a string of junk being passed to pcre_compile() if the pattern was longer
2905: than about 50K.
2906:
2907: 17. I have done a major re-factoring of the way pcre_compile() computes the
2908: amount of memory needed for a compiled pattern. Previously, there was code
2909: that made a preliminary scan of the pattern in order to do this. That was
2910: OK when PCRE was new, but as the facilities have expanded, it has become
2911: harder and harder to keep it in step with the real compile phase, and there
2912: have been a number of bugs (see for example, 4 above). I have now found a
2913: cunning way of running the real compile function in a "fake" mode that
2914: enables it to compute how much memory it would need, while actually only
2915: ever using a few hundred bytes of working memory and without too many
2916: tests of the mode. This should make future maintenance and development
2917: easier. A side effect of this work is that the limit of 200 on the nesting
2918: depth of parentheses has been removed (though this was never a serious
2919: limitation, I suspect). However, there is a downside: pcre_compile() now
2920: runs more slowly than before (30% or more, depending on the pattern). I
2921: hope this isn't a big issue. There is no effect on runtime performance.
2922:
2923: 18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
2924: newline (only possible for the last line of a file) and it was a
2925: pattern that set a locale (followed by /Lsomething), pcretest crashed.
2926:
2927: 19. Added additional timing features to pcretest. (1) The -tm option now times
2928: matching only, not compiling. (2) Both -t and -tm can be followed, as a
2929: separate command line item, by a number that specifies the number of
2930: repeats to use when timing. The default is 50000; this gives better
2931: precision, but takes uncomfortably long for very large patterns.
2932:
2933: 20. Extended pcre_study() to be more clever in cases where a branch of a
2934: subpattern has no definite first character. For example, (a*|b*)[cd] would
2935: previously give no result from pcre_study(). Now it recognizes that the
2936: first character must be a, b, c, or d.
2937:
2938: 21. There was an incorrect error "recursive call could loop indefinitely" if
2939: a subpattern (or the entire pattern) that was being tested for matching an
2940: empty string contained only one non-empty item after a nested subpattern.
2941: For example, the pattern (?>\x{100}*)\d(?R) provoked this error
2942: incorrectly, because the \d was being skipped in the check.
2943:
2944: 22. The pcretest program now has a new pattern option /B and a command line
2945: option -b, which is equivalent to adding /B to every pattern. This causes
2946: it to show the compiled bytecode, without the additional information that
2947: -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
2948: is the same as /B/I).
2949:
2950: 23. A new optimization is now able automatically to treat some sequences such
2951: as a*b as a*+b. More specifically, if something simple (such as a character
2952: or a simple class like \d) has an unlimited quantifier, and is followed by
2953: something that cannot possibly match the quantified thing, the quantifier
2954: is automatically "possessified".
2955:
2956: 24. A recursive reference to a subpattern whose number was greater than 39
2957: went wrong under certain circumstances in UTF-8 mode. This bug could also
2958: have affected the operation of pcre_study().
2959:
2960: 25. Realized that a little bit of performance could be had by replacing
2961: (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
2962:
2963: 26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
2964:
2965: 27. Possessive quantifiers such as a++ were previously implemented by turning
2966: them into atomic groups such as ($>a+). Now they have their own opcodes,
2967: which improves performance. This includes the automatically created ones
2968: from 23 above.
2969:
2970: 28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
2971: lookahead was broken if it was not anchored. PCRE was mistakenly expecting
2972: the first matched character to be a colon. This applied both to named and
2973: numbered groups.
2974:
2975: 29. The ucpinternal.h header file was missing its idempotency #ifdef.
2976:
2977: 30. I was sent a "project" file called libpcre.a.dev which I understand makes
2978: building PCRE on Windows easier, so I have included it in the distribution.
2979:
2980: 31. There is now a check in pcretest against a ridiculously large number being
2981: returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
2982: loop, the loop is abandoned.
2983:
2984: 32. Forward references to subpatterns in conditions such as (?(2)...) where
2985: subpattern 2 is defined later cause pcre_compile() to search forwards in
2986: the pattern for the relevant set of parentheses. This search went wrong
2987: when there were unescaped parentheses in a character class, parentheses
2988: escaped with \Q...\E, or parentheses in a #-comment in /x mode.
2989:
2990: 33. "Subroutine" calls and backreferences were previously restricted to
2991: referencing subpatterns earlier in the regex. This restriction has now
2992: been removed.
2993:
2994: 34. Added a number of extra features that are going to be in Perl 5.10. On the
2995: whole, these are just syntactic alternatives for features that PCRE had
2996: previously implemented using the Python syntax or my own invention. The
2997: other formats are all retained for compatibility.
2998:
2999: (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
3000: as (?P<name>...). The new forms, as well as being in Perl 5.10, are
3001: also .NET compatible.
3002:
3003: (b) A recursion or subroutine call to a named group can now be defined as
3004: (?&name) as well as (?P>name).
3005:
3006: (c) A backreference to a named group can now be defined as \k<name> or
3007: \k'name' as well as (?P=name). The new forms, as well as being in Perl
3008: 5.10, are also .NET compatible.
3009:
3010: (d) A conditional reference to a named group can now use the syntax
3011: (?(<name>) or (?('name') as well as (?(name).
3012:
3013: (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
3014: groups (named and numbered) that are never evaluated inline, but can be
3015: called as "subroutines" from elsewhere. In effect, the DEFINE condition
3016: is always false. There may be only one alternative in such a group.
3017:
3018: (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
3019: as the simple (?(R). The condition is true only if the most recent
3020: recursion is that of the given number or name. It does not search out
3021: through the entire recursion stack.
3022:
3023: (g) The escape \gN or \g{N} has been added, where N is a positive or
3024: negative number, specifying an absolute or relative reference.
3025:
3026: 35. Tidied to get rid of some further signed/unsigned compiler warnings and
3027: some "unreachable code" warnings.
3028:
3029: 36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
3030: things, this adds five new scripts.
3031:
3032: 37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
3033: There were also incompatibilities regarding the handling of \Q..\E inside
3034: character classes, for example with patterns like [\Qa\E-\Qz\E] where the
3035: hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
3036:
3037: 38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
3038: matches an empty string, and forcibly breaks the loop. There were bugs in
3039: this code in non-simple cases. For a pattern such as ^(a()*)* matched
3040: against aaaa the result was just "a" rather than "aaaa", for example. Two
3041: separate and independent bugs (that affected different cases) have been
3042: fixed.
3043:
3044: 39. Refactored the code to abolish the use of different opcodes for small
3045: capturing bracket numbers. This is a tidy that I avoided doing when I
3046: removed the limit on the number of capturing brackets for 3.5 back in 2001.
3047: The new approach is not only tidier, it makes it possible to reduce the
3048: memory needed to fix the previous bug (38).
3049:
3050: 40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
3051: sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
3052: processing dot, circumflex, or dollar metacharacters, or #-comments in /x
3053: mode.
3054:
3055: 41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
3056: report.
3057:
3058: 42. Applied patch, originally from Ari Pollak, modified by Google, to allow
3059: copy construction and assignment in the C++ wrapper.
3060:
3061: 43. Updated pcregrep to support "--newline=any". In the process, I fixed a
3062: couple of bugs that could have given wrong results in the "--newline=crlf"
3063: case.
3064:
3065: 44. Added a number of casts and did some reorganization of signed/unsigned int
3066: variables following suggestions from Dair Grant. Also renamed the variable
3067: "this" as "item" because it is a C++ keyword.
3068:
3069: 45. Arranged for dftables to add
3070:
3071: #include "pcre_internal.h"
3072:
3073: to pcre_chartables.c because without it, gcc 4.x may remove the array
3074: definition from the final binary if PCRE is built into a static library and
3075: dead code stripping is activated.
3076:
3077: 46. For an unanchored pattern, if a match attempt fails at the start of a
3078: newline sequence, and the newline setting is CRLF or ANY, and the next two
3079: characters are CRLF, advance by two characters instead of one.
3080:
3081:
3082: Version 6.7 04-Jul-06
3083: ---------------------
3084:
3085: 1. In order to handle tests when input lines are enormously long, pcretest has
3086: been re-factored so that it automatically extends its buffers when
3087: necessary. The code is crude, but this _is_ just a test program. The
3088: default size has been increased from 32K to 50K.
3089:
3090: 2. The code in pcre_study() was using the value of the re argument before
3091: testing it for NULL. (Of course, in any sensible call of the function, it
3092: won't be NULL.)
3093:
3094: 3. The memmove() emulation function in pcre_internal.h, which is used on
3095: systems that lack both memmove() and bcopy() - that is, hardly ever -
3096: was missing a "static" storage class specifier.
3097:
3098: 4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
3099: containing an extended class (one that cannot be represented by a bitmap
3100: because it contains high-valued characters or Unicode property items, e.g.
3101: [\pZ]). Almost always one would set UTF-8 mode when processing such a
3102: pattern, but PCRE should not loop if you do not (it no longer does).
3103: [Detail: two cases were found: (a) a repeated subpattern containing an
3104: extended class; (b) a recursive reference to a subpattern that followed a
3105: previous extended class. It wasn't skipping over the extended class
3106: correctly when UTF-8 mode was not set.]
3107:
3108: 5. A negated single-character class was not being recognized as fixed-length
3109: in lookbehind assertions such as (?<=[^f]), leading to an incorrect
3110: compile error "lookbehind assertion is not fixed length".
3111:
3112: 6. The RunPerlTest auxiliary script was showing an unexpected difference
3113: between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
3114: write a Perl script that can interpret lines of an input file either as
3115: byte characters or as UTF-8, which is what "perltest" was being required to
3116: do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
3117: can't do is switch easily at run time between having the "use utf8;" pragma
3118: or not. In the end, I fudged it by using the RunPerlTest script to insert
3119: "use utf8;" explicitly for the UTF-8 tests.
3120:
3121: 7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
3122: the end of the subject string, contrary to the documentation and to what
3123: Perl does. This was true of both matching functions. Now it matches only at
3124: the start of the subject and immediately after *internal* newlines.
3125:
3126: 8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
3127: a pointer to an int instead of a pointer to an unsigned long int. This
3128: caused problems on 64-bit systems.
3129:
3130: 9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
3131: instance of the 'standard' template library not being so standard".
3132:
3133: 10. There was no check on the number of named subpatterns nor the maximum
3134: length of a subpattern name. The product of these values is used to compute
3135: the size of the memory block for a compiled pattern. By supplying a very
3136: long subpattern name and a large number of named subpatterns, the size
3137: computation could be caused to overflow. This is now prevented by limiting
3138: the length of names to 32 characters, and the number of named subpatterns
3139: to 10,000.
3140:
3141: 11. Subpatterns that are repeated with specific counts have to be replicated in
3142: the compiled pattern. The size of memory for this was computed from the
3143: length of the subpattern and the repeat count. The latter is limited to
3144: 65535, but there was no limit on the former, meaning that integer overflow
3145: could in principle occur. The compiled length of a repeated subpattern is
3146: now limited to 30,000 bytes in order to prevent this.
3147:
3148: 12. Added the optional facility to have named substrings with the same name.
3149:
3150: 13. Added the ability to use a named substring as a condition, using the
3151: Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
3152: are numbers (not recommended). Forward references are permitted.
3153:
3154: 14. Added forward references in named backreferences (if you see what I mean).
3155:
3156: 15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
3157: pattern could run off the end of the subject. For example, the pattern
3158: "(?s)(.{1,5})"8 did this with the subject "ab".
3159:
3160: 16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
3161: PCRE_CASELESS was set when matching characters that were quantified with ?
3162: or *.
3163:
3164: 17. A character class other than a single negated character that had a minimum
3165: but no maximum quantifier - for example [ab]{6,} - was not handled
3166: correctly by pce_dfa_exec(). It would match only one character.
3167:
3168: 18. A valid (though odd) pattern that looked like a POSIX character
3169: class but used an invalid character after [ (for example [[,abc,]]) caused
3170: pcre_compile() to give the error "Failed: internal error: code overflow" or
3171: in some cases to crash with a glibc free() error. This could even happen if
3172: the pattern terminated after [[ but there just happened to be a sequence of
3173: letters, a binary zero, and a closing ] in the memory that followed.
3174:
3175: 19. Perl's treatment of octal escapes in the range \400 to \777 has changed
3176: over the years. Originally (before any Unicode support), just the bottom 8
3177: bits were taken. Thus, for example, \500 really meant \100. Nowadays the
3178: output from "man perlunicode" includes this:
3179:
3180: The regular expression compiler produces polymorphic opcodes. That
3181: is, the pattern adapts to the data and automatically switches to
3182: the Unicode character scheme when presented with Unicode data--or
3183: instead uses a traditional byte scheme when presented with byte
3184: data.
3185:
3186: Sadly, a wide octal escape does not cause a switch, and in a string with
3187: no other multibyte characters, these octal escapes are treated as before.
3188: Thus, in Perl, the pattern /\500/ actually matches \100 but the pattern
3189: /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
3190: Unicode string.
3191:
3192: I have not perpetrated such confusion in PCRE. Up till now, it took just
3193: the bottom 8 bits, as in old Perl. I have now made octal escapes with
3194: values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
3195: translate to the appropriate multibyte character.
3196:
3197: 29. Applied some refactoring to reduce the number of warnings from Microsoft
3198: and Borland compilers. This has included removing the fudge introduced
3199: seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
3200: a warning about an unused variable.
3201:
3202: 21. PCRE has not included VT (character 0x0b) in the set of whitespace
3203: characters since release 4.0, because Perl (from release 5.004) does not.
3204: [Or at least, is documented not to: some releases seem to be in conflict
3205: with the documentation.] However, when a pattern was studied with
3206: pcre_study() and all its branches started with \s, PCRE still included VT
3207: as a possible starting character. Of course, this did no harm; it just
3208: caused an unnecessary match attempt.
3209:
3210: 22. Removed a now-redundant internal flag bit that recorded the fact that case
3211: dependency changed within the pattern. This was once needed for "required
3212: byte" processing, but is no longer used. This recovers a now-scarce options
3213: bit. Also moved the least significant internal flag bit to the most-
3214: significant bit of the word, which was not previously used (hangover from
3215: the days when it was an int rather than a uint) to free up another bit for
3216: the future.
3217:
3218: 23. Added support for CRLF line endings as well as CR and LF. As well as the
3219: default being selectable at build time, it can now be changed at runtime
3220: via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
3221: specify that it is scanning data with non-default line endings.
3222:
3223: 24. Changed the definition of CXXLINK to make it agree with the definition of
3224: LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
3225:
3226: 25. Applied Ian Taylor's patches to avoid using another stack frame for tail
3227: recursions. This makes a big different to stack usage for some patterns.
3228:
3229: 26. If a subpattern containing a named recursion or subroutine reference such
3230: as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
3231: the space required for the compiled pattern went wrong and gave too small a
3232: value. Depending on the environment, this could lead to "Failed: internal
3233: error: code overflow at offset 49" or "glibc detected double free or
3234: corruption" errors.
3235:
3236: 27. Applied patches from Google (a) to support the new newline modes and (b) to
3237: advance over multibyte UTF-8 characters in GlobalReplace.
3238:
3239: 28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
3240: difference for some implementation of PCRE in some Windows version.
3241:
3242: 29. Added some extra testing facilities to pcretest:
3243:
3244: \q<number> in a data line sets the "match limit" value
3245: \Q<number> in a data line sets the "match recursion limt" value
3246: -S <number> sets the stack size, where <number> is in megabytes
3247:
3248: The -S option isn't available for Windows.
3249:
3250:
3251: Version 6.6 06-Feb-06
3252: ---------------------
3253:
3254: 1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
3255: in pcreposix.h. I have copied the definition from pcre.h.
3256:
3257: 2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
3258: because pcre.h is no longer a built file.
3259:
3260: 3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
3261: not normally included in the compiled code.
3262:
3263:
3264: Version 6.5 01-Feb-06
3265: ---------------------
3266:
3267: 1. When using the partial match feature with pcre_dfa_exec(), it was not
3268: anchoring the second and subsequent partial matches at the new starting
3269: point. This could lead to incorrect results. For example, with the pattern
3270: /1234/, partially matching against "123" and then "a4" gave a match.
3271:
3272: 2. Changes to pcregrep:
3273:
3274: (a) All non-match returns from pcre_exec() were being treated as failures
3275: to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
3276: error message is output. Some extra information is given for the
3277: PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
3278: probably the only errors that are likely to be caused by users (by
3279: specifying a regex that has nested indefinite repeats, for instance).
3280: If there are more than 20 of these errors, pcregrep is abandoned.
3281:
3282: (b) A binary zero was treated as data while matching, but terminated the
3283: output line if it was written out. This has been fixed: binary zeroes
3284: are now no different to any other data bytes.
3285:
3286: (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
3287: used to set a locale for matching. The --locale=xxxx long option has
3288: been added (no short equivalent) to specify a locale explicitly on the
3289: pcregrep command, overriding the environment variables.
3290:
3291: (d) When -B was used with -n, some line numbers in the output were one less
3292: than they should have been.
3293:
3294: (e) Added the -o (--only-matching) option.
3295:
3296: (f) If -A or -C was used with -c (count only), some lines of context were
3297: accidentally printed for the final match.
3298:
3299: (g) Added the -H (--with-filename) option.
3300:
3301: (h) The combination of options -rh failed to suppress file names for files
3302: that were found from directory arguments.
3303:
3304: (i) Added the -D (--devices) and -d (--directories) options.
3305:
3306: (j) Added the -F (--fixed-strings) option.
3307:
3308: (k) Allow "-" to be used as a file name for -f as well as for a data file.
3309:
3310: (l) Added the --colo(u)r option.
3311:
3312: (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
3313: is not present by default.
3314:
3315: 3. A nasty bug was discovered in the handling of recursive patterns, that is,
3316: items such as (?R) or (?1), when the recursion could match a number of
3317: alternatives. If it matched one of the alternatives, but subsequently,
3318: outside the recursion, there was a failure, the code tried to back up into
3319: the recursion. However, because of the way PCRE is implemented, this is not
3320: possible, and the result was an incorrect result from the match.
3321:
3322: In order to prevent this happening, the specification of recursion has
3323: been changed so that all such subpatterns are automatically treated as
3324: atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
3325:
3326: 4. I had overlooked the fact that, in some locales, there are characters for
3327: which isalpha() is true but neither isupper() nor islower() are true. In
3328: the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
3329: and ordfeminine) are like this. This affected the treatment of \w and \W
3330: when they appeared in character classes, but not when they appeared outside
3331: a character class. The bit map for "word" characters is now created
3332: separately from the results of isalnum() instead of just taking it from the
3333: upper, lower, and digit maps. (Plus the underscore character, of course.)
3334:
3335: 5. The above bug also affected the handling of POSIX character classes such as
3336: [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
3337: permanent tables. Instead, the bit maps for such a class were previously
3338: created as the appropriate unions of the upper, lower, and digit bitmaps.
3339: Now they are created by subtraction from the [[:word:]] class, which has
3340: its own bitmap.
3341:
3342: 6. The [[:blank:]] character class matches horizontal, but not vertical space.
3343: It is created by subtracting the vertical space characters (\x09, \x0a,
3344: \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
3345: subtraction was done in the overall bitmap for a character class, meaning
3346: that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
3347: be recognized. This bug has been fixed.
3348:
3349: 7. Patches from the folks at Google:
3350:
3351: (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
3352: real life, but is still worth protecting against".
3353:
3354: (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
3355: regular expressions".
3356:
3357: (c) pcre_scanner.cc: avoid use of std::count() because not all systems
3358: have it.
3359:
3360: (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
3361: "configure" and the latter not, in order to fix a problem somebody had
3362: with compiling the Arg class on HP-UX.
3363:
3364: (e) Improve the error-handling of the C++ wrapper a little bit.
3365:
3366: (f) New tests for checking recursion limiting.
3367:
3368: 8. The pcre_memmove() function, which is used only if the environment does not
3369: have a standard memmove() function (and is therefore rarely compiled),
3370: contained two bugs: (a) use of int instead of size_t, and (b) it was not
3371: returning a result (though PCRE never actually uses the result).
3372:
3373: 9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
3374: large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
3375: returned instead of calling malloc() with an overflowing number that would
3376: most likely cause subsequent chaos.
3377:
3378: 10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
3379:
3380: 11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
3381: with this option is matched, the nmatch and pmatch options of regexec() are
3382: ignored.
3383:
3384: 12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
3385: provided in case anyone wants to the the POSIX interface with UTF-8
3386: strings.
3387:
3388: 13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
3389: C++ linking (needed for some HP-UX environments).
3390:
3391: 14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
3392: (unused parameter) and in the pcre_printint() function (omitted "default"
3393: switch label when the default is to do nothing).
3394:
3395: 15. Added some code to make it possible, when PCRE is compiled as a C++
3396: library, to replace subject pointers for pcre_exec() with a smart pointer
3397: class, thus making it possible to process discontinuous strings.
3398:
3399: 16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
3400: much the same function. They were added by different people who were trying
3401: to make PCRE easy to compile on non-Unix systems. It has been suggested
3402: that PCRE_EXPORT be abolished now that there is more automatic apparatus
3403: for compiling on Windows systems. I have therefore replaced it with
3404: PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
3405: defaults to "extern" for C or "extern C" for C++, which works fine on
3406: Unix-like systems. It is now possible to override the value of PCRE_DATA_
3407: SCOPE with something explicit in config.h. In addition:
3408:
3409: (a) pcreposix.h still had just "extern" instead of either of these macros;
3410: I have replaced it with PCRE_DATA_SCOPE.
3411:
3412: (b) Functions such as _pcre_xclass(), which are internal to the library,
3413: but external in the C sense, all had PCRE_EXPORT in their definitions.
3414: This is apparently wrong for the Windows case, so I have removed it.
3415: (It makes no difference on Unix-like systems.)
3416:
3417: 17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
3418: of recursive calls to match(). This is different to MATCH_LIMIT because
3419: that limits the total number of calls to match(), not all of which increase
3420: the depth of recursion. Limiting the recursion depth limits the amount of
3421: stack (or heap if NO_RECURSE is set) that is used. The default can be set
3422: when PCRE is compiled, and changed at run time. A patch from Google adds
3423: this functionality to the C++ interface.
3424:
3425: 18. Changes to the handling of Unicode character properties:
3426:
3427: (a) Updated the table to Unicode 4.1.0.
3428:
3429: (b) Recognize characters that are not in the table as "Cn" (undefined).
3430:
3431: (c) I revised the way the table is implemented to a much improved format
3432: which includes recognition of ranges. It now supports the ranges that
3433: are defined in UnicodeData.txt, and it also amalgamates other
3434: characters into ranges. This has reduced the number of entries in the
3435: table from around 16,000 to around 3,000, thus reducing its size
3436: considerably. I realized I did not need to use a tree structure after
3437: all - a binary chop search is just as efficient. Having reduced the
3438: number of entries, I extended their size from 6 bytes to 8 bytes to
3439: allow for more data.
3440:
3441: (d) Added support for Unicode script names via properties such as \p{Han}.
3442:
3443: 19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
3444: matching that character.
3445:
3446: 20. When matching a repeated Unicode property with a minimum greater than zero,
3447: (for example \pL{2,}), PCRE could look past the end of the subject if it
3448: reached it while seeking the minimum number of characters. This could
3449: happen only if some of the characters were more than one byte long, because
3450: there is a check for at least the minimum number of bytes.
3451:
3452: 21. Refactored the implementation of \p and \P so as to be more general, to
3453: allow for more different types of property in future. This has changed the
3454: compiled form incompatibly. Anybody with saved compiled patterns that use
3455: \p or \P will have to recompile them.
3456:
3457: 22. Added "Any" and "L&" to the supported property types.
3458:
3459: 23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
3460: but give a compile time error if the value is greater than 0xff.
3461:
3462: 24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
3463: accidentally not being installed or uninstalled.
3464:
3465: 25. The pcre.h file was built from pcre.h.in, but the only changes that were
3466: made were to insert the current release number. This seemed silly, because
3467: it made things harder for people building PCRE on systems that don't run
3468: "configure". I have turned pcre.h into a distributed file, no longer built
3469: by "configure", with the version identification directly included. There is
3470: no longer a pcre.h.in file.
3471:
3472: However, this change necessitated a change to the pcre-config script as
3473: well. It is built from pcre-config.in, and one of the substitutions was the
3474: release number. I have updated configure.ac so that ./configure now finds
3475: the release number by grepping pcre.h.
3476:
3477: 26. Added the ability to run the tests under valgrind.
3478:
3479:
3480: Version 6.4 05-Sep-05
3481: ---------------------
3482:
3483: 1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
3484: "--" to be printed when multiple files were scanned, even when none of the
3485: -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
3486: consider it to be a bug, and have restored the previous behaviour.
3487:
3488: 2. A couple of code tidies to get rid of compiler warnings.
3489:
3490: 3. The pcretest program used to cheat by referring to symbols in the library
3491: whose names begin with _pcre_. These are internal symbols that are not
3492: really supposed to be visible externally, and in some environments it is
3493: possible to suppress them. The cheating is now confined to including
3494: certain files from the library's source, which is a bit cleaner.
3495:
3496: 4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
3497: file's purpose clearer.
3498:
3499: 5. Reorganized pcre_ucp_findchar().
3500:
3501:
3502: Version 6.3 15-Aug-05
3503: ---------------------
3504:
3505: 1. The file libpcre.pc.in did not have general read permission in the tarball.
3506:
3507: 2. There were some problems when building without C++ support:
3508:
3509: (a) If C++ support was not built, "make install" and "make test" still
3510: tried to test it.
3511:
3512: (b) There were problems when the value of CXX was explicitly set. Some
3513: changes have been made to try to fix these, and ...
3514:
3515: (c) --disable-cpp can now be used to explicitly disable C++ support.
3516:
3517: (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
3518: backslash in a target when C++ was disabled. This confuses some
3519: versions of "make", apparently. Using an intermediate variable solves
3520: this. (Same for CPP_LOBJ.)
3521:
3522: 3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
3523: (non-Windows) now includes $(CFLAGS) because these flags are sometimes
3524: necessary on certain architectures.
3525:
3526: 4. Added a setting of -export-symbols-regex to the link command to remove
3527: those symbols that are exported in the C sense, but actually are local
3528: within the library, and not documented. Their names all begin with
3529: "_pcre_". This is not a perfect job, because (a) we have to except some
3530: symbols that pcretest ("illegally") uses, and (b) the facility isn't always
3531: available (and never for static libraries). I have made a note to try to
3532: find a way round (a) in the future.
3533:
3534:
3535: Version 6.2 01-Aug-05
3536: ---------------------
3537:
3538: 1. There was no test for integer overflow of quantifier values. A construction
3539: such as {1111111111111111} would give undefined results. What is worse, if
3540: a minimum quantifier for a parenthesized subpattern overflowed and became
3541: negative, the calculation of the memory size went wrong. This could have
3542: led to memory overwriting.
3543:
3544: 2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
3545:
3546: 3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
3547: operating environments where this matters.
3548:
3549: 4. Applied Giuseppe Maxia's patch to add additional features for controlling
3550: PCRE options from within the C++ wrapper.
3551:
3552: 5. Named capturing subpatterns were not being correctly counted when a pattern
3553: was compiled. This caused two problems: (a) If there were more than 100
3554: such subpatterns, the calculation of the memory needed for the whole
3555: compiled pattern went wrong, leading to an overflow error. (b) Numerical
3556: back references of the form \12, where the number was greater than 9, were
3557: not recognized as back references, even though there were sufficient
3558: previous subpatterns.
3559:
3560: 6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
3561: versions of gcc, e.g. 2.95.4.
3562:
3563:
3564: Version 6.1 21-Jun-05
3565: ---------------------
3566:
3567: 1. There was one reference to the variable "posix" in pcretest.c that was not
3568: surrounded by "#if !defined NOPOSIX".
3569:
3570: 2. Make it possible to compile pcretest without DFA support, UTF8 support, or
3571: the cross-check on the old pcre_info() function, for the benefit of the
3572: cut-down version of PCRE that is currently imported into Exim.
3573:
3574: 3. A (silly) pattern starting with (?i)(?-i) caused an internal space
3575: allocation error. I've done the easy fix, which wastes 2 bytes for sensible
3576: patterns that start (?i) but I don't think that matters. The use of (?i) is
3577: just an example; this all applies to the other options as well.
3578:
3579: 4. Since libtool seems to echo the compile commands it is issuing, the output
3580: from "make" can be reduced a bit by putting "@" in front of each libtool
3581: compile command.
3582:
3583: 5. Patch from the folks at Google for configure.in to be a bit more thorough
3584: in checking for a suitable C++ installation before trying to compile the
3585: C++ stuff. This should fix a reported problem when a compiler was present,
3586: but no suitable headers.
3587:
3588: 6. The man pages all had just "PCRE" as their title. I have changed them to
3589: be the relevant file name. I have also arranged that these names are
3590: retained in the file doc/pcre.txt, which is a concatenation in text format
3591: of all the man pages except the little individual ones for each function.
3592:
3593: 7. The NON-UNIX-USE file had not been updated for the different set of source
3594: files that come with release 6. I also added a few comments about the C++
3595: wrapper.
3596:
3597:
3598: Version 6.0 07-Jun-05
3599: ---------------------
3600:
3601: 1. Some minor internal re-organization to help with my DFA experiments.
3602:
3603: 2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
3604: didn't matter for the library itself when fully configured, but did matter
3605: when compiling without UCP support, or within Exim, where the ucp files are
3606: not imported.
3607:
3608: 3. Refactoring of the library code to split up the various functions into
3609: different source modules. The addition of the new DFA matching code (see
3610: below) to a single monolithic source would have made it really too
3611: unwieldy, quite apart from causing all the code to be include in a
3612: statically linked application, when only some functions are used. This is
3613: relevant even without the DFA addition now that patterns can be compiled in
3614: one application and matched in another.
3615:
3616: The downside of splitting up is that there have to be some external
3617: functions and data tables that are used internally in different modules of
3618: the library but which are not part of the API. These have all had their
3619: names changed to start with "_pcre_" so that they are unlikely to clash
3620: with other external names.
3621:
3622: 4. Added an alternate matching function, pcre_dfa_exec(), which matches using
3623: a different (DFA) algorithm. Although it is slower than the original
3624: function, it does have some advantages for certain types of matching
3625: problem.
3626:
3627: 5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
3628: including restarting after a partial match.
3629:
3630: 6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
3631: defined when compiling for Windows was sent to me. I have put it into the
3632: code, though I have no means of testing or verifying it.
3633:
3634: 7. Added the pcre_refcount() auxiliary function.
3635:
3636: 8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
3637: match before or at the first newline in the subject string. In pcretest,
3638: the /f option on a pattern can be used to set this.
3639:
3640: 9. A repeated \w when used in UTF-8 mode with characters greater than 256
3641: would behave wrongly. This has been present in PCRE since release 4.0.
3642:
3643: 10. A number of changes to the pcregrep command:
3644:
3645: (a) Refactored how -x works; insert ^(...)$ instead of setting
3646: PCRE_ANCHORED and checking the length, in preparation for adding
3647: something similar for -w.
3648:
3649: (b) Added the -w (match as a word) option.
3650:
3651: (c) Refactored the way lines are read and buffered so as to have more
3652: than one at a time available.
3653:
3654: (d) Implemented a pcregrep test script.
3655:
3656: (e) Added the -M (multiline match) option. This allows patterns to match
3657: over several lines of the subject. The buffering ensures that at least
3658: 8K, or the rest of the document (whichever is the shorter) is available
3659: for matching (and similarly the previous 8K for lookbehind assertions).
3660:
3661: (f) Changed the --help output so that it now says
3662:
3663: -w, --word-regex(p)
3664:
3665: instead of two lines, one with "regex" and the other with "regexp"
3666: because that confused at least one person since the short forms are the
3667: same. (This required a bit of code, as the output is generated
3668: automatically from a table. It wasn't just a text change.)
3669:
3670: (g) -- can be used to terminate pcregrep options if the next thing isn't an
3671: option but starts with a hyphen. Could be a pattern or a path name
3672: starting with a hyphen, for instance.
3673:
3674: (h) "-" can be given as a file name to represent stdin.
3675:
3676: (i) When file names are being printed, "(standard input)" is used for
3677: the standard input, for compatibility with GNU grep. Previously
3678: "<stdin>" was used.
3679:
3680: (j) The option --label=xxx can be used to supply a name to be used for
3681: stdin when file names are being printed. There is no short form.
3682:
3683: (k) Re-factored the options decoding logic because we are going to add
3684: two more options that take data. Such options can now be given in four
3685: different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
3686:
3687: (l) Added the -A, -B, and -C options for requesting that lines of context
3688: around matches be printed.
3689:
3690: (m) Added the -L option to print the names of files that do not contain
3691: any matching lines, that is, the complement of -l.
3692:
3693: (n) The return code is 2 if any file cannot be opened, but pcregrep does
3694: continue to scan other files.
3695:
3696: (o) The -s option was incorrectly implemented. For compatibility with other
3697: greps, it now suppresses the error message for a non-existent or non-
3698: accessible file (but not the return code). There is a new option called
3699: -q that suppresses the output of matching lines, which was what -s was
3700: previously doing.
3701:
3702: (p) Added --include and --exclude options to specify files for inclusion
3703: and exclusion when recursing.
3704:
3705: 11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
3706: Hopefully, it now does.
3707:
3708: 12. Missing cast in pcre_study().
3709:
3710: 13. Added an "uninstall" target to the makefile.
3711:
3712: 14. Replaced "extern" in the function prototypes in Makefile.in with
3713: "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
3714: world, but is set differently for Windows.
3715:
3716: 15. Added a second compiling function called pcre_compile2(). The only
3717: difference is that it has an extra argument, which is a pointer to an
3718: integer error code. When there is a compile-time failure, this is set
3719: non-zero, in addition to the error test pointer being set to point to an
3720: error message. The new argument may be NULL if no error number is required
3721: (but then you may as well call pcre_compile(), which is now just a
3722: wrapper). This facility is provided because some applications need a
3723: numeric error indication, but it has also enabled me to tidy up the way
3724: compile-time errors are handled in the POSIX wrapper.
3725:
3726: 16. Added VPATH=.libs to the makefile; this should help when building with one
3727: prefix path and installing with another. (Or so I'm told by someone who
3728: knows more about this stuff than I do.)
3729:
3730: 17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
3731: passes PCRE_DOTALL to the pcre_compile() function, making the "." character
3732: match everything, including newlines. This is not POSIX-compatible, but
3733: somebody wanted the feature. From pcretest it can be activated by using
3734: both the P and the s flags.
3735:
3736: 18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
3737:
3738: 19. libpcre.pc was being incorrectly installed as executable.
3739:
3740: 20. A couple of places in pcretest check for end-of-line by looking for '\n';
3741: it now also looks for '\r' so that it will work unmodified on Windows.
3742:
3743: 21. Added Google's contributed C++ wrapper to the distribution.
3744:
3745: 22. Added some untidy missing memory free() calls in pcretest, to keep
3746: Electric Fence happy when testing.
3747:
3748:
3749:
3750: Version 5.0 13-Sep-04
3751: ---------------------
3752:
3753: 1. Internal change: literal characters are no longer packed up into items
3754: containing multiple characters in a single byte-string. Each character
3755: is now matched using a separate opcode. However, there may be more than one
3756: byte in the character in UTF-8 mode.
3757:
3758: 2. The pcre_callout_block structure has two new fields: pattern_position and
3759: next_item_length. These contain the offset in the pattern to the next match
3760: item, and its length, respectively.
3761:
3762: 3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
3763: insertion of callouts before each pattern item. Added the /C option to
3764: pcretest to make use of this.
3765:
3766: 4. On the advice of a Windows user, the lines
3767:
3768: #if defined(_WIN32) || defined(WIN32)
3769: _setmode( _fileno( stdout ), 0x8000 );
3770: #endif /* defined(_WIN32) || defined(WIN32) */
3771:
3772: have been added to the source of pcretest. This apparently does useful
3773: magic in relation to line terminators.
3774:
3775: 5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
3776: for the benefit of those environments where the "b" makes a difference.
3777:
3778: 6. The icc compiler has the same options as gcc, but "configure" doesn't seem
3779: to know about it. I have put a hack into configure.in that adds in code
3780: to set GCC=yes if CC=icc. This seems to end up at a point in the
3781: generated configure script that is early enough to affect the setting of
3782: compiler options, which is what is needed, but I have no means of testing
3783: whether it really works. (The user who reported this had patched the
3784: generated configure script, which of course I cannot do.)
3785:
3786: LATER: After change 22 below (new libtool files), the configure script
3787: seems to know about icc (and also ecc). Therefore, I have commented out
3788: this hack in configure.in.
3789:
3790: 7. Added support for pkg-config (2 patches were sent in).
3791:
3792: 8. Negated POSIX character classes that used a combination of internal tables
3793: were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
3794: [[:^ascii]]. Typically, they would match almost any characters. The other
3795: POSIX classes were not broken in this way.
3796:
3797: 9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
3798: to find the match, as PCRE was deluded into thinking that the match had to
3799: start at the start point or following a newline. The same bug applied to
3800: patterns with negative forward assertions or any backward assertions
3801: preceding ".*" at the start, unless the pattern required a fixed first
3802: character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
3803:
3804: 10. In UTF-8 mode, when moving forwards in the subject after a failed match
3805: starting at the last subject character, bytes beyond the end of the subject
3806: string were read.
3807:
3808: 11. Renamed the variable "class" as "classbits" to make life easier for C++
3809: users. (Previously there was a macro definition, but it apparently wasn't
3810: enough.)
3811:
3812: 12. Added the new field "tables" to the extra data so that tables can be passed
3813: in at exec time, or the internal tables can be re-selected. This allows
3814: a compiled regex to be saved and re-used at a later time by a different
3815: program that might have everything at different addresses.
3816:
3817: 13. Modified the pcre-config script so that, when run on Solaris, it shows a
3818: -R library as well as a -L library.
3819:
3820: 14. The debugging options of pcretest (-d on the command line or D on a
3821: pattern) showed incorrect output for anything following an extended class
3822: that contained multibyte characters and which was followed by a quantifier.
3823:
3824: 15. Added optional support for general category Unicode character properties
3825: via the \p, \P, and \X escapes. Unicode property support implies UTF-8
3826: support. It adds about 90K to the size of the library. The meanings of the
3827: inbuilt class escapes such as \d and \s have NOT been changed.
3828:
3829: 16. Updated pcredemo.c to include calls to free() to release the memory for the
3830: compiled pattern.
3831:
3832: 17. The generated file chartables.c was being created in the source directory
3833: instead of in the building directory. This caused the build to fail if the
3834: source directory was different from the building directory, and was
3835: read-only.
3836:
3837: 18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
3838: file. No doubt somebody will tell me if they don't make sense... Also added
3839: Dan Mooney's comments about building on OpenVMS.
3840:
3841: 19. Added support for partial matching via the PCRE_PARTIAL option for
3842: pcre_exec() and the \P data escape in pcretest.
3843:
3844: 20. Extended pcretest with 3 new pattern features:
3845:
3846: (i) A pattern option of the form ">rest-of-line" causes pcretest to
3847: write the compiled pattern to the file whose name is "rest-of-line".
3848: This is a straight binary dump of the data, with the saved pointer to
3849: the character tables forced to be NULL. The study data, if any, is
3850: written too. After writing, pcretest reads a new pattern.
3851:
3852: (ii) If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
3853: compiled pattern from the given file. There must not be any
3854: occurrences of "<" in the file name (pretty unlikely); if there are,
3855: pcretest will instead treat the initial "<" as a pattern delimiter.
3856: After reading in the pattern, pcretest goes on to read data lines as
3857: usual.
3858:
3859: (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
3860: and 16-bit fields in a compiled pattern, to simulate a pattern that
3861: was compiled on a host of opposite endianness.
3862:
3863: 21. The pcre-exec() function can now cope with patterns that were compiled on
3864: hosts of opposite endianness, with this restriction:
3865:
3866: As for any compiled expression that is saved and used later, the tables
3867: pointer field cannot be preserved; the extra_data field in the arguments
3868: to pcre_exec() should be used to pass in a tables address if a value
3869: other than the default internal tables were used at compile time.
3870:
3871: 22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
3872: now diagnosed as an error. Previously, most of the time, a negative number
3873: would have been treated as zero, but if in addition "ovector" was passed as
3874: NULL, a crash could occur.
3875:
3876: 23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
3877: new versions from the libtool 1.5 distribution (the last one is a copy of
3878: a file called libtool.m4). This seems to have fixed the need to patch
3879: "configure" to support Darwin 1.3 (which I used to do). However, I still
3880: had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
3881: workstation).
3882:
3883: 24. Changed the PCRE licence to be the more standard "BSD" licence.
3884:
3885:
3886: Version 4.5 01-Dec-03
3887: ---------------------
3888:
3889: 1. There has been some re-arrangement of the code for the match() function so
3890: that it can be compiled in a version that does not call itself recursively.
3891: Instead, it keeps those local variables that need separate instances for
3892: each "recursion" in a frame on the heap, and gets/frees frames whenever it
3893: needs to "recurse". Keeping track of where control must go is done by means
3894: of setjmp/longjmp. The whole thing is implemented by a set of macros that
3895: hide most of the details from the main code, and operates only if
3896: NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
3897: "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
3898: operating.
3899:
3900: To make it easier for callers to provide specially tailored get/free
3901: functions for this usage, two new functions, pcre_stack_malloc, and
3902: pcre_stack_free, are used. They are always called in strict stacking order,
3903: and the size of block requested is always the same.
3904:
3905: The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
3906: PCRE has been compiled to use the stack or the heap for recursion. The
3907: -C option of pcretest uses this to show which version is compiled.
3908:
3909: A new data escape \S, is added to pcretest; it causes the amounts of store
3910: obtained and freed by both kinds of malloc/free at match time to be added
3911: to the output.
3912:
3913: 2. Changed the locale test to use "fr_FR" instead of "fr" because that's
3914: what's available on my current Linux desktop machine.
3915:
3916: 3. When matching a UTF-8 string, the test for a valid string at the start has
3917: been extended. If start_offset is not zero, PCRE now checks that it points
3918: to a byte that is the start of a UTF-8 character. If not, it returns
3919: PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
3920: this is necessary because there may be backward assertions in the pattern.
3921: When matching the same subject several times, it may save resources to use
3922: PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
3923:
3924: 4. The code for checking the validity of UTF-8 strings has been tightened so
3925: that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
3926: containing "overlong sequences".
3927:
3928: 5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
3929: I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
3930: should have been "&", but it just so happened that all the cases this let
3931: through by mistake were picked up later in the function.
3932:
3933: 6. I had used a variable called "isblank" - this is a C99 function, causing
3934: some compilers to warn. To avoid this, I renamed it (as "blankclass").
3935:
3936: 7. Cosmetic: (a) only output another newline at the end of pcretest if it is
3937: prompting; (b) run "./pcretest /dev/null" at the start of the test script
3938: so the version is shown; (c) stop "make test" echoing "./RunTest".
3939:
3940: 8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
3941:
3942: 9. The prototype for memmove() for systems that don't have it was using
3943: size_t, but the inclusion of the header that defines size_t was later. I've
3944: moved the #includes for the C headers earlier to avoid this.
3945:
3946: 10. Added some adjustments to the code to make it easier to compiler on certain
3947: special systems:
3948:
3949: (a) Some "const" qualifiers were missing.
3950: (b) Added the macro EXPORT before all exported functions; by default this
3951: is defined to be empty.
3952: (c) Changed the dftables auxiliary program (that builds chartables.c) so
3953: that it reads its output file name as an argument instead of writing
3954: to the standard output and assuming this can be redirected.
3955:
3956: 11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
3957: class containing characters with values greater than 255, PCRE compilation
3958: went into a loop.
3959:
3960: 12. A recursive reference to a subpattern that was within another subpattern
3961: that had a minimum quantifier of zero caused PCRE to crash. For example,
3962: (x(y(?2))z)? provoked this bug with a subject that got as far as the
3963: recursion. If the recursively-called subpattern itself had a zero repeat,
3964: that was OK.
3965:
3966: 13. In pcretest, the buffer for reading a data line was set at 30K, but the
3967: buffer into which it was copied (for escape processing) was still set at
3968: 1024, so long lines caused crashes.
3969:
3970: 14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
3971: "internal error: code overflow...". This applied to any character class
3972: that was followed by a possessive quantifier.
3973:
3974: 15. Modified the Makefile to add libpcre.la as a prerequisite for
3975: libpcreposix.la because I was told this is needed for a parallel build to
3976: work.
3977:
3978: 16. If a pattern that contained .* following optional items at the start was
3979: studied, the wrong optimizing data was generated, leading to matching
3980: errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
3981: matching string must start with a or b or c. The correct conclusion for
3982: this pattern is that a match can start with any character.
3983:
3984:
3985: Version 4.4 13-Aug-03
3986: ---------------------
3987:
3988: 1. In UTF-8 mode, a character class containing characters with values between
3989: 127 and 255 was not handled correctly if the compiled pattern was studied.
3990: In fixing this, I have also improved the studying algorithm for such
3991: classes (slightly).
3992:
3993: 2. Three internal functions had redundant arguments passed to them. Removal
3994: might give a very teeny performance improvement.
3995:
3996: 3. Documentation bug: the value of the capture_top field in a callout is *one
3997: more than* the number of the hightest numbered captured substring.
3998:
3999: 4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
4000: in incorrectly linking with a previously installed version. They now link
4001: explicitly with libpcre.la.
4002:
4003: 5. configure.in no longer needs to recognize Cygwin specially.
4004:
4005: 6. A problem in pcre.in for Windows platforms is fixed.
4006:
4007: 7. If a pattern was successfully studied, and the -d (or /D) flag was given to
4008: pcretest, it used to include the size of the study block as part of its
4009: output. Unfortunately, the structure contains a field that has a different
4010: size on different hardware architectures. This meant that the tests that
4011: showed this size failed. As the block is currently always of a fixed size,
4012: this information isn't actually particularly useful in pcretest output, so
4013: I have just removed it.
4014:
4015: 8. Three pre-processor statements accidentally did not start in column 1.
4016: Sadly, there are *still* compilers around that complain, even though
4017: standard C has not required this for well over a decade. Sigh.
4018:
4019: 9. In pcretest, the code for checking callouts passed small integers in the
4020: callout_data field, which is a void * field. However, some picky compilers
4021: complained about the casts involved for this on 64-bit systems. Now
4022: pcretest passes the address of the small integer instead, which should get
4023: rid of the warnings.
4024:
4025: 10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
4026: both compile and run time, and gives an error if an invalid UTF-8 sequence
4027: is found. There is a option for disabling this check in cases where the
4028: string is known to be correct and/or the maximum performance is wanted.
4029:
4030: 11. In response to a bug report, I changed one line in Makefile.in from
4031:
4032: -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
4033: to
4034: -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
4035:
4036: to look similar to other lines, but I have no way of telling whether this
4037: is the right thing to do, as I do not use Windows. No doubt I'll get told
4038: if it's wrong...
4039:
4040:
4041: Version 4.3 21-May-03
4042: ---------------------
4043:
4044: 1. Two instances of @WIN_PREFIX@ omitted from the Windows targets in the
4045: Makefile.
4046:
4047: 2. Some refactoring to improve the quality of the code:
4048:
4049: (i) The utf8_table... variables are now declared "const".
4050:
4051: (ii) The code for \cx, which used the "case flipping" table to upper case
4052: lower case letters, now just substracts 32. This is ASCII-specific,
4053: but the whole concept of \cx is ASCII-specific, so it seems
4054: reasonable.
4055:
4056: (iii) PCRE was using its character types table to recognize decimal and
4057: hexadecimal digits in the pattern. This is silly, because it handles
4058: only 0-9, a-f, and A-F, but the character types table is locale-
4059: specific, which means strange things might happen. A private
4060: table is now used for this - though it costs 256 bytes, a table is
4061: much faster than multiple explicit tests. Of course, the standard
4062: character types table is still used for matching digits in subject
4063: strings against \d.
4064:
4065: (iv) Strictly, the identifier ESC_t is reserved by POSIX (all identifiers
4066: ending in _t are). So I've renamed it as ESC_tee.
4067:
4068: 3. The first argument for regexec() in the POSIX wrapper should have been
4069: defined as "const".
4070:
4071: 4. Changed pcretest to use malloc() for its buffers so that they can be
4072: Electric Fenced for debugging.
4073:
4074: 5. There were several places in the code where, in UTF-8 mode, PCRE would try
4075: to read one or more bytes before the start of the subject string. Often this
4076: had no effect on PCRE's behaviour, but in some circumstances it could
4077: provoke a segmentation fault.
4078:
4079: 6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
4080: to try to read one or more bytes before the start of the subject string.
4081:
4082: 7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
4083: UTF-8 support could misbehave in various ways if the subject string
4084: contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
4085: area. (PCRE was not checking for the UTF-8 mode flag, and trying to move
4086: back over UTF-8 characters.)
4087:
4088:
4089: Version 4.2 14-Apr-03
4090: ---------------------
4091:
4092: 1. Typo "#if SUPPORT_UTF8" instead of "#ifdef SUPPORT_UTF8" fixed.
4093:
4094: 2. Changes to the building process, supplied by Ronald Landheer-Cieslak
4095: [ON_WINDOWS]: new variable, "#" on non-Windows platforms
4096: [NOT_ON_WINDOWS]: new variable, "#" on Windows platforms
4097: [WIN_PREFIX]: new variable, "cyg" for Cygwin
4098: * Makefile.in: use autoconf substitution for OBJEXT, EXEEXT, BUILD_OBJEXT
4099: and BUILD_EXEEXT
4100: Note: automatic setting of the BUILD variables is not yet working
4101: set CPPFLAGS and BUILD_CPPFLAGS (but don't use yet) - should be used at
4102: compile-time but not at link-time
4103: [LINK]: use for linking executables only
4104: make different versions for Windows and non-Windows
4105: [LINKLIB]: new variable, copy of UNIX-style LINK, used for linking
4106: libraries
4107: [LINK_FOR_BUILD]: new variable
4108: [OBJEXT]: use throughout
4109: [EXEEXT]: use throughout
4110: <winshared>: new target
4111: <wininstall>: new target
4112: <dftables.o>: use native compiler
4113: <dftables>: use native linker
4114: <install>: handle Windows platform correctly
4115: <clean>: ditto
4116: <check>: ditto
4117: copy DLL to top builddir before testing
4118:
4119: As part of these changes, -no-undefined was removed again. This was reported
4120: to give trouble on HP-UX 11.0, so getting rid of it seems like a good idea
4121: in any case.
4122:
4123: 3. Some tidies to get rid of compiler warnings:
4124:
4125: . In the match_data structure, match_limit was an unsigned long int, whereas
4126: match_call_count was an int. I've made them both unsigned long ints.
4127:
4128: . In pcretest the fact that a const uschar * doesn't automatically cast to
4129: a void * provoked a warning.
4130:
4131: . Turning on some more compiler warnings threw up some "shadow" variables
4132: and a few more missing casts.
4133:
4134: 4. If PCRE was complied with UTF-8 support, but called without the PCRE_UTF8
4135: option, a class that contained a single character with a value between 128
4136: and 255 (e.g. /[\xFF]/) caused PCRE to crash.
4137:
4138: 5. If PCRE was compiled with UTF-8 support, but called without the PCRE_UTF8
4139: option, a class that contained several characters, but with at least one
4140: whose value was between 128 and 255 caused PCRE to crash.
4141:
4142:
4143: Version 4.1 12-Mar-03
4144: ---------------------
4145:
4146: 1. Compiling with gcc -pedantic found a couple of places where casts were
4147: needed, and a string in dftables.c that was longer than standard compilers are
4148: required to support.
4149:
4150: 2. Compiling with Sun's compiler found a few more places where the code could
4151: be tidied up in order to avoid warnings.
4152:
4153: 3. The variables for cross-compiling were called HOST_CC and HOST_CFLAGS; the
4154: first of these names is deprecated in the latest Autoconf in favour of the name
4155: CC_FOR_BUILD, because "host" is typically used to mean the system on which the
4156: compiled code will be run. I can't find a reference for HOST_CFLAGS, but by
4157: analogy I have changed it to CFLAGS_FOR_BUILD.
4158:
4159: 4. Added -no-undefined to the linking command in the Makefile, because this is
4160: apparently helpful for Windows. To make it work, also added "-L. -lpcre" to the
4161: linking step for the pcreposix library.
4162:
4163: 5. PCRE was failing to diagnose the case of two named groups with the same
4164: name.
4165:
4166: 6. A problem with one of PCRE's optimizations was discovered. PCRE remembers a
4167: literal character that is needed in the subject for a match, and scans along to
4168: ensure that it is present before embarking on the full matching process. This
4169: saves time in cases of nested unlimited repeats that are never going to match.
4170: Problem: the scan can take a lot of time if the subject is very long (e.g.
4171: megabytes), thus penalizing straightforward matches. It is now done only if the
4172: amount of subject to be scanned is less than 1000 bytes.
4173:
4174: 7. A lesser problem with the same optimization is that it was recording the
4175: first character of an anchored pattern as "needed", thus provoking a search
4176: right along the subject, even when the first match of the pattern was going to
4177: fail. The "needed" character is now not set for anchored patterns, unless it
4178: follows something in the pattern that is of non-fixed length. Thus, it still
4179: fulfils its original purpose of finding quick non-matches in cases of nested
4180: unlimited repeats, but isn't used for simple anchored patterns such as /^abc/.
4181:
4182:
4183: Version 4.0 17-Feb-03
4184: ---------------------
4185:
4186: 1. If a comment in an extended regex that started immediately after a meta-item
4187: extended to the end of string, PCRE compiled incorrect data. This could lead to
4188: all kinds of weird effects. Example: /#/ was bad; /()#/ was bad; /a#/ was not.
4189:
4190: 2. Moved to autoconf 2.53 and libtool 1.4.2.
4191:
4192: 3. Perl 5.8 no longer needs "use utf8" for doing UTF-8 things. Consequently,
4193: the special perltest8 script is no longer needed - all the tests can be run
4194: from a single perltest script.
4195:
4196: 4. From 5.004, Perl has not included the VT character (0x0b) in the set defined
4197: by \s. It has now been removed in PCRE. This means it isn't recognized as
4198: whitespace in /x regexes too, which is the same as Perl. Note that the POSIX
4199: class [:space:] *does* include VT, thereby creating a mess.
4200:
4201: 5. Added the class [:blank:] (a GNU extension from Perl 5.8) to match only
4202: space and tab.
4203:
4204: 6. Perl 5.005 was a long time ago. It's time to amalgamate the tests that use
4205: its new features into the main test script, reducing the number of scripts.
4206:
4207: 7. Perl 5.8 has changed the meaning of patterns like /a(?i)b/. Earlier versions
4208: were backward compatible, and made the (?i) apply to the whole pattern, as if
4209: /i were given. Now it behaves more logically, and applies the option setting
4210: only to what follows. PCRE has been changed to follow suit. However, if it
4211: finds options settings right at the start of the pattern, it extracts them into
4212: the global options, as before. Thus, they show up in the info data.
4213:
4214: 8. Added support for the \Q...\E escape sequence. Characters in between are
4215: treated as literals. This is slightly different from Perl in that $ and @ are
4216: also handled as literals inside the quotes. In Perl, they will cause variable
4217: interpolation. Note the following examples:
4218:
4219: Pattern PCRE matches Perl matches
4220:
4221: \Qabc$xyz\E abc$xyz abc followed by the contents of $xyz
4222: \Qabc\$xyz\E abc\$xyz abc\$xyz
4223: \Qabc\E\$\Qxyz\E abc$xyz abc$xyz
4224:
4225: For compatibility with Perl, \Q...\E sequences are recognized inside character
4226: classes as well as outside them.
4227:
4228: 9. Re-organized 3 code statements in pcretest to avoid "overflow in
4229: floating-point constant arithmetic" warnings from a Microsoft compiler. Added a
4230: (size_t) cast to one statement in pcretest and one in pcreposix to avoid
4231: signed/unsigned warnings.
4232:
4233: 10. SunOS4 doesn't have strtoul(). This was used only for unpicking the -o
4234: option for pcretest, so I've replaced it by a simple function that does just
4235: that job.
4236:
4237: 11. pcregrep was ending with code 0 instead of 2 for the commands "pcregrep" or
4238: "pcregrep -".
4239:
4240: 12. Added "possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's
4241: Java package. This provides some syntactic sugar for simple cases of what my
4242: documentation calls "once-only subpatterns". A pattern such as x*+ is the same
4243: as (?>x*). In other words, if what is inside (?>...) is just a single repeated
4244: item, you can use this simplified notation. Note that only makes sense with
4245: greedy quantifiers. Consequently, the use of the possessive quantifier forces
4246: greediness, whatever the setting of the PCRE_UNGREEDY option.
4247:
4248: 13. A change of greediness default within a pattern was not taking effect at
4249: the current level for patterns like /(b+(?U)a+)/. It did apply to parenthesized
4250: subpatterns that followed. Patterns like /b+(?U)a+/ worked because the option
4251: was abstracted outside.
4252:
4253: 14. PCRE now supports the \G assertion. It is true when the current matching
4254: position is at the start point of the match. This differs from \A when the
4255: starting offset is non-zero. Used with the /g option of pcretest (or similar
4256: code), it works in the same way as it does for Perl's /g option. If all
4257: alternatives of a regex begin with \G, the expression is anchored to the start
4258: match position, and the "anchored" flag is set in the compiled expression.
4259:
4260: 15. Some bugs concerning the handling of certain option changes within patterns
4261: have been fixed. These applied to options other than (?ims). For example,
4262: "a(?x: b c )d" did not match "XabcdY" but did match "Xa b c dY". It should have
4263: been the other way round. Some of this was related to change 7 above.
4264:
4265: 16. PCRE now gives errors for /[.x.]/ and /[=x=]/ as unsupported POSIX
4266: features, as Perl does. Previously, PCRE gave the warnings only for /[[.x.]]/
4267: and /[[=x=]]/. PCRE now also gives an error for /[:name:]/ because it supports
4268: POSIX classes only within a class (e.g. /[[:alpha:]]/).
4269:
4270: 17. Added support for Perl's \C escape. This matches one byte, even in UTF8
4271: mode. Unlike ".", it always matches newline, whatever the setting of
4272: PCRE_DOTALL. However, PCRE does not permit \C to appear in lookbehind
4273: assertions. Perl allows it, but it doesn't (in general) work because it can't
4274: calculate the length of the lookbehind. At least, that's the case for Perl
4275: 5.8.0 - I've been told they are going to document that it doesn't work in
4276: future.
4277:
4278: 18. Added an error diagnosis for escapes that PCRE does not support: these are
4279: \L, \l, \N, \P, \p, \U, \u, and \X.
4280:
4281: 19. Although correctly diagnosing a missing ']' in a character class, PCRE was
4282: reading past the end of the pattern in cases such as /[abcd/.
4283:
4284: 20. PCRE was getting more memory than necessary for patterns with classes that
4285: contained both POSIX named classes and other characters, e.g. /[[:space:]abc/.
4286:
4287: 21. Added some code, conditional on #ifdef VPCOMPAT, to make life easier for
4288: compiling PCRE for use with Virtual Pascal.
4289:
4290: 22. Small fix to the Makefile to make it work properly if the build is done
4291: outside the source tree.
4292:
4293: 23. Added a new extension: a condition to go with recursion. If a conditional
4294: subpattern starts with (?(R) the "true" branch is used if recursion has
4295: happened, whereas the "false" branch is used only at the top level.
4296:
4297: 24. When there was a very long string of literal characters (over 255 bytes
4298: without UTF support, over 250 bytes with UTF support), the computation of how
4299: much memory was required could be incorrect, leading to segfaults or other
4300: strange effects.
4301:
4302: 25. PCRE was incorrectly assuming anchoring (either to start of subject or to
4303: start of line for a non-DOTALL pattern) when a pattern started with (.*) and
4304: there was a subsequent back reference to those brackets. This meant that, for
4305: example, /(.*)\d+\1/ failed to match "abc123bc". Unfortunately, it isn't
4306: possible to check for precisely this case. All we can do is abandon the
4307: optimization if .* occurs inside capturing brackets when there are any back
4308: references whatsoever. (See below for a better fix that came later.)
4309:
4310: 26. The handling of the optimization for finding the first character of a
4311: non-anchored pattern, and for finding a character that is required later in the
4312: match were failing in some cases. This didn't break the matching; it just
4313: failed to optimize when it could. The way this is done has been re-implemented.
4314:
4315: 27. Fixed typo in error message for invalid (?R item (it said "(?p").
4316:
4317: 28. Added a new feature that provides some of the functionality that Perl
4318: provides with (?{...}). The facility is termed a "callout". The way it is done
4319: in PCRE is for the caller to provide an optional function, by setting
4320: pcre_callout to its entry point. Like pcre_malloc and pcre_free, this is a
4321: global variable. By default it is unset, which disables all calling out. To get
4322: the function called, the regex must include (?C) at appropriate points. This
4323: is, in fact, equivalent to (?C0), and any number <= 255 may be given with (?C).
4324: This provides a means of identifying different callout points. When PCRE
4325: reaches such a point in the regex, if pcre_callout has been set, the external
4326: function is called. It is provided with data in a structure called
4327: pcre_callout_block, which is defined in pcre.h. If the function returns 0,
4328: matching continues; if it returns a non-zero value, the match at the current
4329: point fails. However, backtracking will occur if possible. [This was changed
4330: later and other features added - see item 49 below.]
4331:
4332: 29. pcretest is upgraded to test the callout functionality. It provides a
4333: callout function that displays information. By default, it shows the start of
4334: the match and the current position in the text. There are some new data escapes
4335: to vary what happens:
4336:
4337: \C+ in addition, show current contents of captured substrings
4338: \C- do not supply a callout function
4339: \C!n return 1 when callout number n is reached
4340: \C!n!m return 1 when callout number n is reached for the mth time
4341:
4342: 30. If pcregrep was called with the -l option and just a single file name, it
4343: output "<stdin>" if a match was found, instead of the file name.
4344:
4345: 31. Improve the efficiency of the POSIX API to PCRE. If the number of capturing
4346: slots is less than POSIX_MALLOC_THRESHOLD, use a block on the stack to pass to
4347: pcre_exec(). This saves a malloc/free per call. The default value of
4348: POSIX_MALLOC_THRESHOLD is 10; it can be changed by --with-posix-malloc-threshold
4349: when configuring.
4350:
4351: 32. The default maximum size of a compiled pattern is 64K. There have been a
4352: few cases of people hitting this limit. The code now uses macros to handle the
4353: storing of links as offsets within the compiled pattern. It defaults to 2-byte
4354: links, but this can be changed to 3 or 4 bytes by --with-link-size when
4355: configuring. Tests 2 and 5 work only with 2-byte links because they output
4356: debugging information about compiled patterns.
4357:
4358: 33. Internal code re-arrangements:
4359:
4360: (a) Moved the debugging function for printing out a compiled regex into
4361: its own source file (printint.c) and used #include to pull it into
4362: pcretest.c and, when DEBUG is defined, into pcre.c, instead of having two
4363: separate copies.
4364:
4365: (b) Defined the list of op-code names for debugging as a macro in
4366: internal.h so that it is next to the definition of the opcodes.
4367:
4368: (c) Defined a table of op-code lengths for simpler skipping along compiled
4369: code. This is again a macro in internal.h so that it is next to the
4370: definition of the opcodes.
4371:
4372: 34. Added support for recursive calls to individual subpatterns, along the
4373: lines of Robin Houston's patch (but implemented somewhat differently).
4374:
4375: 35. Further mods to the Makefile to help Win32. Also, added code to pcregrep to
4376: allow it to read and process whole directories in Win32. This code was
4377: contributed by Lionel Fourquaux; it has not been tested by me.
4378:
4379: 36. Added support for named subpatterns. The Python syntax (?P<name>...) is
4380: used to name a group. Names consist of alphanumerics and underscores, and must
4381: be unique. Back references use the syntax (?P=name) and recursive calls use
4382: (?P>name) which is a PCRE extension to the Python extension. Groups still have
4383: numbers. The function pcre_fullinfo() can be used after compilation to extract
4384: a name/number map. There are three relevant calls:
4385:
4386: PCRE_INFO_NAMEENTRYSIZE yields the size of each entry in the map
4387: PCRE_INFO_NAMECOUNT yields the number of entries
4388: PCRE_INFO_NAMETABLE yields a pointer to the map.
4389:
4390: The map is a vector of fixed-size entries. The size of each entry depends on
4391: the length of the longest name used. The first two bytes of each entry are the
4392: group number, most significant byte first. There follows the corresponding
4393: name, zero terminated. The names are in alphabetical order.
4394:
4395: 37. Make the maximum literal string in the compiled code 250 for the non-UTF-8
4396: case instead of 255. Making it the same both with and without UTF-8 support
4397: means that the same test output works with both.
4398:
4399: 38. There was a case of malloc(0) in the POSIX testing code in pcretest. Avoid
4400: calling malloc() with a zero argument.
4401:
4402: 39. Change 25 above had to resort to a heavy-handed test for the .* anchoring
4403: optimization. I've improved things by keeping a bitmap of backreferences with
4404: numbers 1-31 so that if .* occurs inside capturing brackets that are not in
4405: fact referenced, the optimization can be applied. It is unlikely that a
4406: relevant occurrence of .* (i.e. one which might indicate anchoring or forcing
4407: the match to follow \n) will appear inside brackets with a number greater than
4408: 31, but if it does, any back reference > 31 suppresses the optimization.
4409:
4410: 40. Added a new compile-time option PCRE_NO_AUTO_CAPTURE. This has the effect
4411: of disabling numbered capturing parentheses. Any opening parenthesis that is
4412: not followed by ? behaves as if it were followed by ?: but named parentheses
4413: can still be used for capturing (and they will acquire numbers in the usual
4414: way).
4415:
4416: 41. Redesigned the return codes from the match() function into yes/no/error so
4417: that errors can be passed back from deep inside the nested calls. A malloc
4418: failure while inside a recursive subpattern call now causes the
4419: PCRE_ERROR_NOMEMORY return instead of quietly going wrong.
4420:
4421: 42. It is now possible to set a limit on the number of times the match()
4422: function is called in a call to pcre_exec(). This facility makes it possible to
4423: limit the amount of recursion and backtracking, though not in a directly
4424: obvious way, because the match() function is used in a number of different
4425: circumstances. The count starts from zero for each position in the subject
4426: string (for non-anchored patterns). The default limit is, for compatibility, a
4427: large number, namely 10 000 000. You can change this in two ways:
4428:
4429: (a) When configuring PCRE before making, you can use --with-match-limit=n
4430: to set a default value for the compiled library.
4431:
4432: (b) For each call to pcre_exec(), you can pass a pcre_extra block in which
4433: a different value is set. See 45 below.
4434:
4435: If the limit is exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
4436:
4437: 43. Added a new function pcre_config(int, void *) to enable run-time extraction
4438: of things that can be changed at compile time. The first argument specifies
4439: what is wanted and the second points to where the information is to be placed.
4440: The current list of available information is:
4441:
4442: PCRE_CONFIG_UTF8
4443:
4444: The output is an integer that is set to one if UTF-8 support is available;
4445: otherwise it is set to zero.
4446:
4447: PCRE_CONFIG_NEWLINE
4448:
4449: The output is an integer that it set to the value of the code that is used for
4450: newline. It is either LF (10) or CR (13).
4451:
4452: PCRE_CONFIG_LINK_SIZE
4453:
4454: The output is an integer that contains the number of bytes used for internal
4455: linkage in compiled expressions. The value is 2, 3, or 4. See item 32 above.
4456:
4457: PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
4458:
4459: The output is an integer that contains the threshold above which the POSIX
4460: interface uses malloc() for output vectors. See item 31 above.
4461:
4462: PCRE_CONFIG_MATCH_LIMIT
4463:
4464: The output is an unsigned integer that contains the default limit of the number
4465: of match() calls in a pcre_exec() execution. See 42 above.
4466:
4467: 44. pcretest has been upgraded by the addition of the -C option. This causes it
4468: to extract all the available output from the new pcre_config() function, and to
4469: output it. The program then exits immediately.
4470:
4471: 45. A need has arisen to pass over additional data with calls to pcre_exec() in
4472: order to support additional features. One way would have been to define
4473: pcre_exec2() (for example) with extra arguments, but this would not have been
4474: extensible, and would also have required all calls to the original function to
4475: be mapped to the new one. Instead, I have chosen to extend the mechanism that
4476: is used for passing in "extra" data from pcre_study().
4477:
4478: The pcre_extra structure is now exposed and defined in pcre.h. It currently
4479: contains the following fields:
4480:
4481: flags a bitmap indicating which of the following fields are set
4482: study_data opaque data from pcre_study()
4483: match_limit a way of specifying a limit on match() calls for a specific
4484: call to pcre_exec()
4485: callout_data data for callouts (see 49 below)
4486:
4487: The flag bits are also defined in pcre.h, and are
4488:
4489: PCRE_EXTRA_STUDY_DATA
4490: PCRE_EXTRA_MATCH_LIMIT
4491: PCRE_EXTRA_CALLOUT_DATA
4492:
4493: The pcre_study() function now returns one of these new pcre_extra blocks, with
4494: the actual study data pointed to by the study_data field, and the
4495: PCRE_EXTRA_STUDY_DATA flag set. This can be passed directly to pcre_exec() as
4496: before. That is, this change is entirely upwards-compatible and requires no
4497: change to existing code.
4498:
4499: If you want to pass in additional data to pcre_exec(), you can either place it
4500: in a pcre_extra block provided by pcre_study(), or create your own pcre_extra
4501: block.
4502:
4503: 46. pcretest has been extended to test the PCRE_EXTRA_MATCH_LIMIT feature. If a
4504: data string contains the escape sequence \M, pcretest calls pcre_exec() several
4505: times with different match limits, until it finds the minimum value needed for
4506: pcre_exec() to complete. The value is then output. This can be instructive; for
4507: most simple matches the number is quite small, but for pathological cases it
4508: gets very large very quickly.
4509:
4510: 47. There's a new option for pcre_fullinfo() called PCRE_INFO_STUDYSIZE. It
4511: returns the size of the data block pointed to by the study_data field in a
4512: pcre_extra block, that is, the value that was passed as the argument to
4513: pcre_malloc() when PCRE was getting memory in which to place the information
4514: created by pcre_study(). The fourth argument should point to a size_t variable.
4515: pcretest has been extended so that this information is shown after a successful
4516: pcre_study() call when information about the compiled regex is being displayed.
4517:
4518: 48. Cosmetic change to Makefile: there's no need to have / after $(DESTDIR)
4519: because what follows is always an absolute path. (Later: it turns out that this
4520: is more than cosmetic for MinGW, because it doesn't like empty path
4521: components.)
4522:
4523: 49. Some changes have been made to the callout feature (see 28 above):
4524:
4525: (i) A callout function now has three choices for what it returns:
4526:
4527: 0 => success, carry on matching
4528: > 0 => failure at this point, but backtrack if possible
4529: < 0 => serious error, return this value from pcre_exec()
4530:
4531: Negative values should normally be chosen from the set of PCRE_ERROR_xxx
4532: values. In particular, returning PCRE_ERROR_NOMATCH forces a standard
4533: "match failed" error. The error number PCRE_ERROR_CALLOUT is reserved for
4534: use by callout functions. It will never be used by PCRE itself.
4535:
4536: (ii) The pcre_extra structure (see 45 above) has a void * field called
4537: callout_data, with corresponding flag bit PCRE_EXTRA_CALLOUT_DATA. The
4538: pcre_callout_block structure has a field of the same name. The contents of
4539: the field passed in the pcre_extra structure are passed to the callout
4540: function in the corresponding field in the callout block. This makes it
4541: easier to use the same callout-containing regex from multiple threads. For
4542: testing, the pcretest program has a new data escape
4543:
4544: \C*n pass the number n (may be negative) as callout_data
4545:
4546: If the callout function in pcretest receives a non-zero value as
4547: callout_data, it returns that value.
4548:
4549: 50. Makefile wasn't handling CFLAGS properly when compiling dftables. Also,
4550: there were some redundant $(CFLAGS) in commands that are now specified as
4551: $(LINK), which already includes $(CFLAGS).
4552:
4553: 51. Extensions to UTF-8 support are listed below. These all apply when (a) PCRE
4554: has been compiled with UTF-8 support *and* pcre_compile() has been compiled
4555: with the PCRE_UTF8 flag. Patterns that are compiled without that flag assume
4556: one-byte characters throughout. Note that case-insensitive matching applies
4557: only to characters whose values are less than 256. PCRE doesn't support the
4558: notion of cases for higher-valued characters.
4559:
4560: (i) A character class whose characters are all within 0-255 is handled as
4561: a bit map, and the map is inverted for negative classes. Previously, a
4562: character > 255 always failed to match such a class; however it should
4563: match if the class was a negative one (e.g. [^ab]). This has been fixed.
4564:
4565: (ii) A negated character class with a single character < 255 is coded as
4566: "not this character" (OP_NOT). This wasn't working properly when the test
4567: character was multibyte, either singly or repeated.
4568:
4569: (iii) Repeats of multibyte characters are now handled correctly in UTF-8
4570: mode, for example: \x{100}{2,3}.
4571:
4572: (iv) The character escapes \b, \B, \d, \D, \s, \S, \w, and \W (either
4573: singly or repeated) now correctly test multibyte characters. However,
4574: PCRE doesn't recognize any characters with values greater than 255 as
4575: digits, spaces, or word characters. Such characters always match \D, \S,
4576: and \W, and never match \d, \s, or \w.
4577:
4578: (v) Classes may now contain characters and character ranges with values
4579: greater than 255. For example: [ab\x{100}-\x{400}].
4580:
4581: (vi) pcregrep now has a --utf-8 option (synonym -u) which makes it call
4582: PCRE in UTF-8 mode.
4583:
4584: 52. The info request value PCRE_INFO_FIRSTCHAR has been renamed
4585: PCRE_INFO_FIRSTBYTE because it is a byte value. However, the old name is
4586: retained for backwards compatibility. (Note that LASTLITERAL is also a byte
4587: value.)
4588:
4589: 53. The single man page has become too large. I have therefore split it up into
4590: a number of separate man pages. These also give rise to individual HTML pages;
4591: these are now put in a separate directory, and there is an index.html page that
4592: lists them all. Some hyperlinking between the pages has been installed.
4593:
4594: 54. Added convenience functions for handling named capturing parentheses.
4595:
4596: 55. Unknown escapes inside character classes (e.g. [\M]) and escapes that
4597: aren't interpreted therein (e.g. [\C]) are literals in Perl. This is now also
4598: true in PCRE, except when the PCRE_EXTENDED option is set, in which case they
4599: are faulted.
4600:
4601: 56. Introduced HOST_CC and HOST_CFLAGS which can be set in the environment when
4602: calling configure. These values are used when compiling the dftables.c program
4603: which is run to generate the source of the default character tables. They
4604: default to the values of CC and CFLAGS. If you are cross-compiling PCRE,
4605: you will need to set these values.
4606:
4607: 57. Updated the building process for Windows DLL, as provided by Fred Cox.
4608:
4609:
4610: Version 3.9 02-Jan-02
4611: ---------------------
4612:
4613: 1. A bit of extraneous text had somehow crept into the pcregrep documentation.
4614:
4615: 2. If --disable-static was given, the building process failed when trying to
4616: build pcretest and pcregrep. (For some reason it was using libtool to compile
4617: them, which is not right, as they aren't part of the library.)
4618:
4619:
4620: Version 3.8 18-Dec-01
4621: ---------------------
4622:
4623: 1. The experimental UTF-8 code was completely screwed up. It was packing the
4624: bytes in the wrong order. How dumb can you get?
4625:
4626:
4627: Version 3.7 29-Oct-01
4628: ---------------------
4629:
4630: 1. In updating pcretest to check change 1 of version 3.6, I screwed up.
4631: This caused pcretest, when used on the test data, to segfault. Unfortunately,
4632: this didn't happen under Solaris 8, where I normally test things.
4633:
4634: 2. The Makefile had to be changed to make it work on BSD systems, where 'make'
4635: doesn't seem to recognize that ./xxx and xxx are the same file. (This entry
4636: isn't in ChangeLog distributed with 3.7 because I forgot when I hastily made
4637: this fix an hour or so after the initial 3.7 release.)
4638:
4639:
4640: Version 3.6 23-Oct-01
4641: ---------------------
4642:
4643: 1. Crashed with /(sens|respons)e and \1ibility/ and "sense and sensibility" if
4644: offsets passed as NULL with zero offset count.
4645:
4646: 2. The config.guess and config.sub files had not been updated when I moved to
4647: the latest autoconf.
4648:
4649:
4650: Version 3.5 15-Aug-01
4651: ---------------------
4652:
4653: 1. Added some missing #if !defined NOPOSIX conditionals in pcretest.c that
4654: had been forgotten.
4655:
4656: 2. By using declared but undefined structures, we can avoid using "void"
4657: definitions in pcre.h while keeping the internal definitions of the structures
4658: private.
4659:
4660: 3. The distribution is now built using autoconf 2.50 and libtool 1.4. From a
4661: user point of view, this means that both static and shared libraries are built
4662: by default, but this can be individually controlled. More of the work of
4663: handling this static/shared cases is now inside libtool instead of PCRE's make
4664: file.
4665:
4666: 4. The pcretest utility is now installed along with pcregrep because it is
4667: useful for users (to test regexs) and by doing this, it automatically gets
4668: relinked by libtool. The documentation has been turned into a man page, so
4669: there are now .1, .txt, and .html versions in /doc.
4670:
4671: 5. Upgrades to pcregrep:
4672: (i) Added long-form option names like gnu grep.
4673: (ii) Added --help to list all options with an explanatory phrase.
4674: (iii) Added -r, --recursive to recurse into sub-directories.
4675: (iv) Added -f, --file to read patterns from a file.
4676:
4677: 6. pcre_exec() was referring to its "code" argument before testing that
4678: argument for NULL (and giving an error if it was NULL).
4679:
4680: 7. Upgraded Makefile.in to allow for compiling in a different directory from
4681: the source directory.
4682:
4683: 8. Tiny buglet in pcretest: when pcre_fullinfo() was called to retrieve the
4684: options bits, the pointer it was passed was to an int instead of to an unsigned
4685: long int. This mattered only on 64-bit systems.
4686:
4687: 9. Fixed typo (3.4/1) in pcre.h again. Sigh. I had changed pcre.h (which is
4688: generated) instead of pcre.in, which it its source. Also made the same change
4689: in several of the .c files.
4690:
4691: 10. A new release of gcc defines printf() as a macro, which broke pcretest
4692: because it had an ifdef in the middle of a string argument for printf(). Fixed
4693: by using separate calls to printf().
4694:
4695: 11. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure
4696: script, to force use of CR or LF instead of \n in the source. On non-Unix
4697: systems, the value can be set in config.h.
4698:
4699: 12. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an
4700: absolute limit. Changed the text of the error message to make this clear, and
4701: likewise updated the man page.
4702:
4703: 13. The limit of 99 on the number of capturing subpatterns has been removed.
4704: The new limit is 65535, which I hope will not be a "real" limit.
4705:
4706:
4707: Version 3.4 22-Aug-00
4708: ---------------------
4709:
4710: 1. Fixed typo in pcre.h: unsigned const char * changed to const unsigned char *.
4711:
4712: 2. Diagnose condition (?(0) as an error instead of crashing on matching.
4713:
4714:
4715: Version 3.3 01-Aug-00
4716: ---------------------
4717:
4718: 1. If an octal character was given, but the value was greater than \377, it
4719: was not getting masked to the least significant bits, as documented. This could
4720: lead to crashes in some systems.
4721:
4722: 2. Perl 5.6 (if not earlier versions) accepts classes like [a-\d] and treats
4723: the hyphen as a literal. PCRE used to give an error; it now behaves like Perl.
4724:
4725: 3. Added the functions pcre_free_substring() and pcre_free_substring_list().
4726: These just pass their arguments on to (pcre_free)(), but they are provided
4727: because some uses of PCRE bind it to non-C systems that can call its functions,
4728: but cannot call free() or pcre_free() directly.
4729:
4730: 4. Add "make test" as a synonym for "make check". Corrected some comments in
4731: the Makefile.
4732:
4733: 5. Add $(DESTDIR)/ in front of all the paths in the "install" target in the
4734: Makefile.
4735:
4736: 6. Changed the name of pgrep to pcregrep, because Solaris has introduced a
4737: command called pgrep for grepping around the active processes.
4738:
4739: 7. Added the beginnings of support for UTF-8 character strings.
4740:
4741: 8. Arranged for the Makefile to pass over the settings of CC, CFLAGS, and
4742: RANLIB to ./ltconfig so that they are used by libtool. I think these are all
4743: the relevant ones. (AR is not passed because ./ltconfig does its own figuring
4744: out for the ar command.)
4745:
4746:
4747: Version 3.2 12-May-00
4748: ---------------------
4749:
4750: This is purely a bug fixing release.
4751:
4752: 1. If the pattern /((Z)+|A)*/ was matched agained ZABCDEFG it matched Z instead
4753: of ZA. This was just one example of several cases that could provoke this bug,
4754: which was introduced by change 9 of version 2.00. The code for breaking
4755: infinite loops after an iteration that matches an empty string was't working
4756: correctly.
4757:
4758: 2. The pcretest program was not imitating Perl correctly for the pattern /a*/g
4759: when matched against abbab (for example). After matching an empty string, it
4760: wasn't forcing anchoring when setting PCRE_NOTEMPTY for the next attempt; this
4761: caused it to match further down the string than it should.
4762:
4763: 3. The code contained an inclusion of sys/types.h. It isn't clear why this
4764: was there because it doesn't seem to be needed, and it causes trouble on some
4765: systems, as it is not a Standard C header. It has been removed.
4766:
4767: 4. Made 4 silly changes to the source to avoid stupid compiler warnings that
4768: were reported on the Macintosh. The changes were from
4769:
4770: while ((c = *(++ptr)) != 0 && c != '\n');
4771: to
4772: while ((c = *(++ptr)) != 0 && c != '\n') ;
4773:
4774: Totally extraordinary, but if that's what it takes...
4775:
4776: 5. PCRE is being used in one environment where neither memmove() nor bcopy() is
4777: available. Added HAVE_BCOPY and an autoconf test for it; if neither
4778: HAVE_MEMMOVE nor HAVE_BCOPY is set, use a built-in emulation function which
4779: assumes the way PCRE uses memmove() (always moving upwards).
4780:
4781: 6. PCRE is being used in one environment where strchr() is not available. There
4782: was only one use in pcre.c, and writing it out to avoid strchr() probably gives
4783: faster code anyway.
4784:
4785:
4786: Version 3.1 09-Feb-00
4787: ---------------------
4788:
4789: The only change in this release is the fixing of some bugs in Makefile.in for
4790: the "install" target:
4791:
4792: (1) It was failing to install pcreposix.h.
4793:
4794: (2) It was overwriting the pcre.3 man page with the pcreposix.3 man page.
4795:
4796:
4797: Version 3.0 01-Feb-00
4798: ---------------------
4799:
4800: 1. Add support for the /+ modifier to perltest (to output $` like it does in
4801: pcretest).
4802:
4803: 2. Add support for the /g modifier to perltest.
4804:
4805: 3. Fix pcretest so that it behaves even more like Perl for /g when the pattern
4806: matches null strings.
4807:
4808: 4. Fix perltest so that it doesn't do unwanted things when fed an empty
4809: pattern. Perl treats empty patterns specially - it reuses the most recent
4810: pattern, which is not what we want. Replace // by /(?#)/ in order to avoid this
4811: effect.
4812:
4813: 5. The POSIX interface was broken in that it was just handing over the POSIX
4814: captured string vector to pcre_exec(), but (since release 2.00) PCRE has
4815: required a bigger vector, with some working space on the end. This means that
4816: the POSIX wrapper now has to get and free some memory, and copy the results.
4817:
4818: 6. Added some simple autoconf support, placing the test data and the
4819: documentation in separate directories, re-organizing some of the
4820: information files, and making it build pcre-config (a GNU standard). Also added
4821: libtool support for building PCRE as a shared library, which is now the
4822: default.
4823:
4824: 7. Got rid of the leading zero in the definition of PCRE_MINOR because 08 and
4825: 09 are not valid octal constants. Single digits will be used for minor values
4826: less than 10.
4827:
4828: 8. Defined REG_EXTENDED and REG_NOSUB as zero in the POSIX header, so that
4829: existing programs that set these in the POSIX interface can use PCRE without
4830: modification.
4831:
4832: 9. Added a new function, pcre_fullinfo() with an extensible interface. It can
4833: return all that pcre_info() returns, plus additional data. The pcre_info()
4834: function is retained for compatibility, but is considered to be obsolete.
4835:
4836: 10. Added experimental recursion feature (?R) to handle one common case that
4837: Perl 5.6 will be able to do with (?p{...}).
4838:
4839: 11. Added support for POSIX character classes like [:alpha:], which Perl is
4840: adopting.
4841:
4842:
4843: Version 2.08 31-Aug-99
4844: ----------------------
4845:
4846: 1. When startoffset was not zero and the pattern began with ".*", PCRE was not
4847: trying to match at the startoffset position, but instead was moving forward to
4848: the next newline as if a previous match had failed.
4849:
4850: 2. pcretest was not making use of PCRE_NOTEMPTY when repeating for /g and /G,
4851: and could get into a loop if a null string was matched other than at the start
4852: of the subject.
4853:
4854: 3. Added definitions of PCRE_MAJOR and PCRE_MINOR to pcre.h so the version can
4855: be distinguished at compile time, and for completeness also added PCRE_DATE.
4856:
4857: 5. Added Paul Sokolovsky's minor changes to make it easy to compile a Win32 DLL
4858: in GnuWin32 environments.
4859:
4860:
4861: Version 2.07 29-Jul-99
4862: ----------------------
4863:
4864: 1. The documentation is now supplied in plain text form and HTML as well as in
4865: the form of man page sources.
4866:
4867: 2. C++ compilers don't like assigning (void *) values to other pointer types.
4868: In particular this affects malloc(). Although there is no problem in Standard
4869: C, I've put in casts to keep C++ compilers happy.
4870:
4871: 3. Typo on pcretest.c; a cast of (unsigned char *) in the POSIX regexec() call
4872: should be (const char *).
4873:
4874: 4. If NOPOSIX is defined, pcretest.c compiles without POSIX support. This may
4875: be useful for non-Unix systems who don't want to bother with the POSIX stuff.
4876: However, I haven't made this a standard facility. The documentation doesn't
4877: mention it, and the Makefile doesn't support it.
4878:
4879: 5. The Makefile now contains an "install" target, with editable destinations at
4880: the top of the file. The pcretest program is not installed.
4881:
4882: 6. pgrep -V now gives the PCRE version number and date.
4883:
4884: 7. Fixed bug: a zero repetition after a literal string (e.g. /abcde{0}/) was
4885: causing the entire string to be ignored, instead of just the last character.
4886:
4887: 8. If a pattern like /"([^\\"]+|\\.)*"/ is applied in the normal way to a
4888: non-matching string, it can take a very, very long time, even for strings of
4889: quite modest length, because of the nested recursion. PCRE now does better in
4890: some of these cases. It does this by remembering the last required literal
4891: character in the pattern, and pre-searching the subject to ensure it is present
4892: before running the real match. In other words, it applies a heuristic to detect
4893: some types of certain failure quickly, and in the above example, if presented
4894: with a string that has no trailing " it gives "no match" very quickly.
4895:
4896: 9. A new runtime option PCRE_NOTEMPTY causes null string matches to be ignored;
4897: other alternatives are tried instead.
4898:
4899:
4900: Version 2.06 09-Jun-99
4901: ----------------------
4902:
4903: 1. Change pcretest's output for amount of store used to show just the code
4904: space, because the remainder (the data block) varies in size between 32-bit and
4905: 64-bit systems.
4906:
4907: 2. Added an extra argument to pcre_exec() to supply an offset in the subject to
4908: start matching at. This allows lookbehinds to work when searching for multiple
4909: occurrences in a string.
4910:
4911: 3. Added additional options to pcretest for testing multiple occurrences:
4912:
4913: /+ outputs the rest of the string that follows a match
4914: /g loops for multiple occurrences, using the new startoffset argument
4915: /G loops for multiple occurrences by passing an incremented pointer
4916:
4917: 4. PCRE wasn't doing the "first character" optimization for patterns starting
4918: with \b or \B, though it was doing it for other lookbehind assertions. That is,
4919: it wasn't noticing that a match for a pattern such as /\bxyz/ has to start with
4920: the letter 'x'. On long subject strings, this gives a significant speed-up.
4921:
4922:
4923: Version 2.05 21-Apr-99
4924: ----------------------
4925:
4926: 1. Changed the type of magic_number from int to long int so that it works
4927: properly on 16-bit systems.
4928:
4929: 2. Fixed a bug which caused patterns starting with .* not to work correctly
4930: when the subject string contained newline characters. PCRE was assuming
4931: anchoring for such patterns in all cases, which is not correct because .* will
4932: not pass a newline unless PCRE_DOTALL is set. It now assumes anchoring only if
4933: DOTALL is set at top level; otherwise it knows that patterns starting with .*
4934: must be retried after every newline in the subject.
4935:
4936:
4937: Version 2.04 18-Feb-99
4938: ----------------------
4939:
4940: 1. For parenthesized subpatterns with repeats whose minimum was zero, the
4941: computation of the store needed to hold the pattern was incorrect (too large).
4942: If such patterns were nested a few deep, this could multiply and become a real
4943: problem.
4944:
4945: 2. Added /M option to pcretest to show the memory requirement of a specific
4946: pattern. Made -m a synonym of -s (which does this globally) for compatibility.
4947:
4948: 3. Subpatterns of the form (regex){n,m} (i.e. limited maximum) were being
4949: compiled in such a way that the backtracking after subsequent failure was
4950: pessimal. Something like (a){0,3} was compiled as (a)?(a)?(a)? instead of
4951: ((a)((a)(a)?)?)? with disastrous performance if the maximum was of any size.
4952:
4953:
4954: Version 2.03 02-Feb-99
4955: ----------------------
4956:
4957: 1. Fixed typo and small mistake in man page.
4958:
4959: 2. Added 4th condition (GPL supersedes if conflict) and created separate
4960: LICENCE file containing the conditions.
4961:
4962: 3. Updated pcretest so that patterns such as /abc\/def/ work like they do in
4963: Perl, that is the internal \ allows the delimiter to be included in the
4964: pattern. Locked out the use of \ as a delimiter. If \ immediately follows
4965: the final delimiter, add \ to the end of the pattern (to test the error).
4966:
4967: 4. Added the convenience functions for extracting substrings after a successful
4968: match. Updated pcretest to make it able to test these functions.
4969:
4970:
4971: Version 2.02 14-Jan-99
4972: ----------------------
4973:
4974: 1. Initialized the working variables associated with each extraction so that
4975: their saving and restoring doesn't refer to uninitialized store.
4976:
4977: 2. Put dummy code into study.c in order to trick the optimizer of the IBM C
4978: compiler for OS/2 into generating correct code. Apparently IBM isn't going to
4979: fix the problem.
4980:
4981: 3. Pcretest: the timing code wasn't using LOOPREPEAT for timing execution
4982: calls, and wasn't printing the correct value for compiling calls. Increased the
4983: default value of LOOPREPEAT, and the number of significant figures in the
4984: times.
4985:
4986: 4. Changed "/bin/rm" in the Makefile to "-rm" so it works on Windows NT.
4987:
4988: 5. Renamed "deftables" as "dftables" to get it down to 8 characters, to avoid
4989: a building problem on Windows NT with a FAT file system.
4990:
4991:
4992: Version 2.01 21-Oct-98
4993: ----------------------
4994:
4995: 1. Changed the API for pcre_compile() to allow for the provision of a pointer
4996: to character tables built by pcre_maketables() in the current locale. If NULL
4997: is passed, the default tables are used.
4998:
4999:
5000: Version 2.00 24-Sep-98
5001: ----------------------
5002:
5003: 1. Since the (>?) facility is in Perl 5.005, don't require PCRE_EXTRA to enable
5004: it any more.
5005:
5006: 2. Allow quantification of (?>) groups, and make it work correctly.
5007:
5008: 3. The first character computation wasn't working for (?>) groups.
5009:
5010: 4. Correct the implementation of \Z (it is permitted to match on the \n at the
5011: end of the subject) and add 5.005's \z, which really does match only at the
5012: very end of the subject.
5013:
5014: 5. Remove the \X "cut" facility; Perl doesn't have it, and (?> is neater.
5015:
5016: 6. Remove the ability to specify CASELESS, MULTILINE, DOTALL, and
5017: DOLLAR_END_ONLY at runtime, to make it possible to implement the Perl 5.005
5018: localized options. All options to pcre_study() were also removed.
5019:
5020: 7. Add other new features from 5.005:
5021:
5022: $(?<= positive lookbehind
5023: $(?<! negative lookbehind
5024: (?imsx-imsx) added the unsetting capability
5025: such a setting is global if at outer level; local otherwise
5026: (?imsx-imsx:) non-capturing groups with option setting
5027: (?(cond)re|re) conditional pattern matching
5028:
5029: A backreference to itself in a repeated group matches the previous
5030: captured string.
5031:
5032: 8. General tidying up of studying (both automatic and via "study")
5033: consequential on the addition of new assertions.
5034:
5035: 9. As in 5.005, unlimited repeated groups that could match an empty substring
5036: are no longer faulted at compile time. Instead, the loop is forcibly broken at
5037: runtime if any iteration does actually match an empty substring.
5038:
5039: 10. Include the RunTest script in the distribution.
5040:
5041: 11. Added tests from the Perl 5.005_02 distribution. This showed up a few
5042: discrepancies, some of which were old and were also with respect to 5.004. They
5043: have now been fixed.
5044:
5045:
5046: Version 1.09 28-Apr-98
5047: ----------------------
5048:
5049: 1. A negated single character class followed by a quantifier with a minimum
5050: value of one (e.g. [^x]{1,6} ) was not compiled correctly. This could lead to
5051: program crashes, or just wrong answers. This did not apply to negated classes
5052: containing more than one character, or to minima other than one.
5053:
5054:
5055: Version 1.08 27-Mar-98
5056: ----------------------
5057:
5058: 1. Add PCRE_UNGREEDY to invert the greediness of quantifiers.
5059:
5060: 2. Add (?U) and (?X) to set PCRE_UNGREEDY and PCRE_EXTRA respectively. The
5061: latter must appear before anything that relies on it in the pattern.
5062:
5063:
5064: Version 1.07 16-Feb-98
5065: ----------------------
5066:
5067: 1. A pattern such as /((a)*)*/ was not being diagnosed as in error (unlimited
5068: repeat of a potentially empty string).
5069:
5070:
5071: Version 1.06 23-Jan-98
5072: ----------------------
5073:
5074: 1. Added Markus Oberhumer's little patches for C++.
5075:
5076: 2. Literal strings longer than 255 characters were broken.
5077:
5078:
5079: Version 1.05 23-Dec-97
5080: ----------------------
5081:
5082: 1. Negated character classes containing more than one character were failing if
5083: PCRE_CASELESS was set at run time.
5084:
5085:
5086: Version 1.04 19-Dec-97
5087: ----------------------
5088:
5089: 1. Corrected the man page, where some "const" qualifiers had been omitted.
5090:
5091: 2. Made debugging output print "{0,xxx}" instead of just "{,xxx}" to agree with
5092: input syntax.
5093:
5094: 3. Fixed memory leak which occurred when a regex with back references was
5095: matched with an offsets vector that wasn't big enough. The temporary memory
5096: that is used in this case wasn't being freed if the match failed.
5097:
5098: 4. Tidied pcretest to ensure it frees memory that it gets.
5099:
5100: 5. Temporary memory was being obtained in the case where the passed offsets
5101: vector was exactly big enough.
5102:
5103: 6. Corrected definition of offsetof() from change 5 below.
5104:
5105: 7. I had screwed up change 6 below and broken the rules for the use of
5106: setjmp(). Now fixed.
5107:
5108:
5109: Version 1.03 18-Dec-97
5110: ----------------------
5111:
5112: 1. A erroneous regex with a missing opening parenthesis was correctly
5113: diagnosed, but PCRE attempted to access brastack[-1], which could cause crashes
5114: on some systems.
5115:
5116: 2. Replaced offsetof(real_pcre, code) by offsetof(real_pcre, code[0]) because
5117: it was reported that one broken compiler failed on the former because "code" is
5118: also an independent variable.
5119:
5120: 3. The erroneous regex a[]b caused an array overrun reference.
5121:
5122: 4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
5123: fail on data ending with that character. (It was going on too far, and checking
5124: the next character, typically a binary zero.) This was specific to the
5125: optimized code for single-character negative classes.
5126:
5127: 5. Added a contributed patch from the TIN world which does the following:
5128:
5129: + Add an undef for memmove, in case the the system defines a macro for it.
5130:
5131: + Add a definition of offsetof(), in case there isn't one. (I don't know
5132: the reason behind this - offsetof() is part of the ANSI standard - but
5133: it does no harm).
5134:
5135: + Reduce the ifdef's in pcre.c using macro DPRINTF, thereby eliminating
5136: most of the places where whitespace preceded '#'. I have given up and
5137: allowed the remaining 2 cases to be at the margin.
5138:
5139: + Rename some variables in pcre to eliminate shadowing. This seems very
5140: pedantic, but does no harm, of course.
5141:
5142: 6. Moved the call to setjmp() into its own function, to get rid of warnings
5143: from gcc -Wall, and avoided calling it at all unless PCRE_EXTRA is used.
5144:
5145: 7. Constructs such as \d{8,} were compiling into the equivalent of
5146: \d{8}\d{0,65527} instead of \d{8}\d* which didn't make much difference to the
5147: outcome, but in this particular case used more store than had been allocated,
5148: which caused the bug to be discovered because it threw up an internal error.
5149:
5150: 8. The debugging code in both pcre and pcretest for outputting the compiled
5151: form of a regex was going wrong in the case of back references followed by
5152: curly-bracketed repeats.
5153:
5154:
5155: Version 1.02 12-Dec-97
5156: ----------------------
5157:
5158: 1. Typos in pcre.3 and comments in the source fixed.
5159:
5160: 2. Applied a contributed patch to get rid of places where it used to remove
5161: 'const' from variables, and fixed some signed/unsigned and uninitialized
5162: variable warnings.
5163:
5164: 3. Added the "runtest" target to Makefile.
5165:
5166: 4. Set default compiler flag to -O2 rather than just -O.
5167:
5168:
5169: Version 1.01 19-Nov-97
5170: ----------------------
5171:
5172: 1. PCRE was failing to diagnose unlimited repeat of empty string for patterns
5173: like /([ab]*)*/, that is, for classes with more than one character in them.
5174:
5175: 2. Likewise, it wasn't diagnosing patterns with "once-only" subpatterns, such
5176: as /((?>a*))*/ (a PCRE_EXTRA facility).
5177:
5178:
5179: Version 1.00 18-Nov-97
5180: ----------------------
5181:
5182: 1. Added compile-time macros to support systems such as SunOS4 which don't have
5183: memmove() or strerror() but have other things that can be used instead.
5184:
5185: 2. Arranged that "make clean" removes the executables.
5186:
5187:
5188: Version 0.99 27-Oct-97
5189: ----------------------
5190:
5191: 1. Fixed bug in code for optimizing classes with only one character. It was
5192: initializing a 32-byte map regardless, which could cause it to run off the end
5193: of the memory it had got.
5194:
5195: 2. Added, conditional on PCRE_EXTRA, the proposed (?>REGEX) construction.
5196:
5197:
5198: Version 0.98 22-Oct-97
5199: ----------------------
5200:
5201: 1. Fixed bug in code for handling temporary memory usage when there are more
5202: back references than supplied space in the ovector. This could cause segfaults.
5203:
5204:
5205: Version 0.97 21-Oct-97
5206: ----------------------
5207:
5208: 1. Added the \X "cut" facility, conditional on PCRE_EXTRA.
5209:
5210: 2. Optimized negated single characters not to use a bit map.
5211:
5212: 3. Brought error texts together as macro definitions; clarified some of them;
5213: fixed one that was wrong - it said "range out of order" when it meant "invalid
5214: escape sequence".
5215:
5216: 4. Changed some char * arguments to const char *.
5217:
5218: 5. Added PCRE_NOTBOL and PCRE_NOTEOL (from POSIX).
5219:
5220: 6. Added the POSIX-style API wrapper in pcreposix.a and testing facilities in
5221: pcretest.
5222:
5223:
5224: Version 0.96 16-Oct-97
5225: ----------------------
5226:
5227: 1. Added a simple "pgrep" utility to the distribution.
5228:
5229: 2. Fixed an incompatibility with Perl: "{" is now treated as a normal character
5230: unless it appears in one of the precise forms "{ddd}", "{ddd,}", or "{ddd,ddd}"
5231: where "ddd" means "one or more decimal digits".
5232:
5233: 3. Fixed serious bug. If a pattern had a back reference, but the call to
5234: pcre_exec() didn't supply a large enough ovector to record the related
5235: identifying subpattern, the match always failed. PCRE now remembers the number
5236: of the largest back reference, and gets some temporary memory in which to save
5237: the offsets during matching if necessary, in order to ensure that
5238: backreferences always work.
5239:
5240: 4. Increased the compatibility with Perl in a number of ways:
5241:
5242: (a) . no longer matches \n by default; an option PCRE_DOTALL is provided
5243: to request this handling. The option can be set at compile or exec time.
5244:
5245: (b) $ matches before a terminating newline by default; an option
5246: PCRE_DOLLAR_ENDONLY is provided to override this (but not in multiline
5247: mode). The option can be set at compile or exec time.
5248:
5249: (c) The handling of \ followed by a digit other than 0 is now supposed to be
5250: the same as Perl's. If the decimal number it represents is less than 10
5251: or there aren't that many previous left capturing parentheses, an octal
5252: escape is read. Inside a character class, it's always an octal escape,
5253: even if it is a single digit.
5254:
5255: (d) An escaped but undefined alphabetic character is taken as a literal,
5256: unless PCRE_EXTRA is set. Currently this just reserves the remaining
5257: escapes.
5258:
5259: (e) {0} is now permitted. (The previous item is removed from the compiled
5260: pattern).
5261:
5262: 5. Changed all the names of code files so that the basic parts are no longer
5263: than 10 characters, and abolished the teeny "globals.c" file.
5264:
5265: 6. Changed the handling of character classes; they are now done with a 32-byte
5266: bit map always.
5267:
5268: 7. Added the -d and /D options to pcretest to make it possible to look at the
5269: internals of compilation without having to recompile pcre.
5270:
5271:
5272: Version 0.95 23-Sep-97
5273: ----------------------
5274:
5275: 1. Fixed bug in pre-pass concerning escaped "normal" characters such as \x5c or
5276: \x20 at the start of a run of normal characters. These were being treated as
5277: real characters, instead of the source characters being re-checked.
5278:
5279:
5280: Version 0.94 18-Sep-97
5281: ----------------------
5282:
5283: 1. The functions are now thread-safe, with the caveat that the global variables
5284: containing pointers to malloc() and free() or alternative functions are the
5285: same for all threads.
5286:
5287: 2. Get pcre_study() to generate a bitmap of initial characters for non-
5288: anchored patterns when this is possible, and use it if passed to pcre_exec().
5289:
5290:
5291: Version 0.93 15-Sep-97
5292: ----------------------
5293:
5294: 1. /(b)|(:+)/ was computing an incorrect first character.
5295:
5296: 2. Add pcre_study() to the API and the passing of pcre_extra to pcre_exec(),
5297: but not actually doing anything yet.
5298:
5299: 3. Treat "-" characters in classes that cannot be part of ranges as literals,
5300: as Perl does (e.g. [-az] or [az-]).
5301:
5302: 4. Set the anchored flag if a branch starts with .* or .*? because that tests
5303: all possible positions.
5304:
5305: 5. Split up into different modules to avoid including unneeded functions in a
5306: compiled binary. However, compile and exec are still in one module. The "study"
5307: function is split off.
5308:
5309: 6. The character tables are now in a separate module whose source is generated
5310: by an auxiliary program - but can then be edited by hand if required. There are
5311: now no calls to isalnum(), isspace(), isdigit(), isxdigit(), tolower() or
5312: toupper() in the code.
5313:
5314: 7. Turn the malloc/free funtions variables into pcre_malloc and pcre_free and
5315: make them global. Abolish the function for setting them, as the caller can now
5316: set them directly.
5317:
5318:
5319: Version 0.92 11-Sep-97
5320: ----------------------
5321:
5322: 1. A repeat with a fixed maximum and a minimum of 1 for an ordinary character
5323: (e.g. /a{1,3}/) was broken (I mis-optimized it).
5324:
5325: 2. Caseless matching was not working in character classes if the characters in
5326: the pattern were in upper case.
5327:
5328: 3. Make ranges like [W-c] work in the same way as Perl for caseless matching.
5329:
5330: 4. Make PCRE_ANCHORED public and accept as a compile option.
5331:
5332: 5. Add an options word to pcre_exec() and accept PCRE_ANCHORED and
5333: PCRE_CASELESS at run time. Add escapes \A and \I to pcretest to cause it to
5334: pass them.
5335:
5336: 6. Give an error if bad option bits passed at compile or run time.
5337:
5338: 7. Add PCRE_MULTILINE at compile and exec time, and (?m) as well. Add \M to
5339: pcretest to cause it to pass that flag.
5340:
5341: 8. Add pcre_info(), to get the number of identifying subpatterns, the stored
5342: options, and the first character, if set.
5343:
5344: 9. Recognize C+ or C{n,m} where n >= 1 as providing a fixed starting character.
5345:
5346:
5347: Version 0.91 10-Sep-97
5348: ----------------------
5349:
5350: 1. PCRE was failing to diagnose unlimited repeats of subpatterns that could
5351: match the empty string as in /(a*)*/. It was looping and ultimately crashing.
5352:
5353: 2. PCRE was looping on encountering an indefinitely repeated back reference to
5354: a subpattern that had matched an empty string, e.g. /(a|)\1*/. It now does what
5355: Perl does - treats the match as successful.
5356:
5357: ****
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to ChangeLog CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / pcre