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

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1438 by ph10, Fri Jan 10 16:13:10 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 02-Aug-2011  Version 8.35-RC1 xx-xxxx-201x
5    -----------------------------
6    
7    1.  A new flag is set, when property checks are present in an XCLASS.
8        When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
10    
11    2.  The auto-possessification of character sets were improved: a normal
12        and an extended character set can be compared now. Furthermore
13        the JIT compiler optimizes more character set checks.
14    
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
17    
18    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
19        of a match later then the end of the match. The pcretest program was not
20        handling the case sensibly - it was outputting from the start to the next
21        binary zero. It now reports this situation in a message, and outputs the
22        text from the end to the start.
23    
24    5.  Fast forward search is improved in JIT. Instead of the first three
25        characters, any three characters with fixed position can be searched.
26        Search order: first, last, middle.
27    
28    6.  Improve character range checks in JIT. Characters are read by an inprecise
29        function now, which returns with an unknown value if the character code is
30        above a certain treshold (e.g: 256). The only limitation is that the value
31        must be bigger than the treshold as well. This function is useful, when
32        the characters above the treshold are handled in the same way.
33    
34    7.  The macros whose names start with RAWUCHAR are placeholders for a future
35        mode in which only the bottom 21 bits of 32-bit data items are used. To
36        make this more memorable for those maintaining the code, the names have
37        been changed to start with UCHAR21, and an extensive comment has been added
38        to their definition.
39    
40    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
41        to the export list in Makefile.am (they were accidentally omitted from the
42        8.34 tarball).
43    
44    9.  The informational output from pcretest used the phrase "starting byte set"
45        which is inappropriate for the 16-bit and 32-bit libraries. As the output
46        for "first char" and "need char" really means "non-UTF-char", I've changed
47        "byte" to "char", and slightly reworded the output. The documentation about
48        these values has also been (I hope) clarified.
49    
50    10. Another JIT related optimization: use table jumps for selecting the correct
51        backtracking path, when more than four alternatives are present inside a
52        bracket.
53    
54    11. Empty match is not possible, when the minimum length is greater than zero,
55        and there is no \K in the pattern. Remove these unnecessary checks form JIT.
56    
57    12. In a caseless character class with UCP support, when a character with more
58        than one alternative case was not the first character of a range, not all
59        the alternative cases were added to the class. For example, s and \x{17f}
60        are both alternative cases for S: the class [RST] was handled correctly,
61        but [R-T] was not.
62    
63    
64    Version 8.34 15-December-2013
65    -----------------------------
66    
67    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
68        executable memory. Patch inspired by Carsten Klein.
69    
70    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
71        this macro is never tested and has no effect, because the work to support
72        coverage involves only compiling and linking options and special targets in
73        the Makefile. The comment in config.h implied that defining the macro would
74        enable coverage support, which is totally false. There was also support for
75        setting this macro in the CMake files (my fault, I just copied it from
76        configure). SUPPORT_GCOV has now been removed.
77    
78    3.  Make a small performance improvement in strlen16() and strlen32() in
79        pcretest.
80    
81    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
82        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
83        these cases). There was also one in pcretest.c.
84    
85    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
86    
87    6.  In UTF mode, the code for checking whether a group could match an empty
88        string (which is used for indefinitely repeated groups to allow for
89        breaking an infinite loop) was broken when the group contained a repeated
90        negated single-character class with a character that occupied more than one
91        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
92        UTF-8 mode). The effect was undefined: the group might or might not be
93        deemed as matching an empty string, or the program might have crashed.
94    
95    7.  The code for checking whether a group could match an empty string was not
96        recognizing that \h, \H, \v, \V, and \R must match a character.
97    
98    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
99        an empty string. If it can, pcretest shows this in its information output.
100    
101    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
102        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
103        matched by pcre_exec() without using JIT:
104    
105        (a) If the rest of the pattern did not match after a maximal run of
106            grapheme clusters, the code for backing up to try with fewer of them
107            did not always back up over a full grapheme when characters that do not
108            have the modifier quality were involved, e.g. Hangul syllables.
109    
110        (b) If the match point in a subject started with modifier character, and
111            there was no match, the code could incorrectly back up beyond the match
112            point, and potentially beyond the first character in the subject,
113            leading to a segfault or an incorrect match result.
114    
115    10. A conditional group with an assertion condition could lead to PCRE
116        recording an incorrect first data item for a match if no other first data
117        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
118        first data item, and therefore matched "ca" after "c" instead of at the
119        start.
120    
121    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
122        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
123    
124    12. The source of pcregrep now includes z/OS-specific code so that it can be
125        compiled for z/OS as part of the special z/OS distribution.
126    
127    13. Added the -T and -TM options to pcretest.
128    
129    14. The code in pcre_compile.c for creating the table of named capturing groups
130        has been refactored. Instead of creating the table dynamically during the
131        actual compiling pass, the information is remembered during the pre-compile
132        pass (on the stack unless there are more than 20 named groups, in which
133        case malloc() is used) and the whole table is created before the actual
134        compile happens. This has simplified the code (it is now nearly 150 lines
135        shorter) and prepared the way for better handling of references to groups
136        with duplicate names.
137    
138    15. A back reference to a named subpattern when there is more than one of the
139        same name now checks them in the order in which they appear in the pattern.
140        The first one that is set is used for the reference. Previously only the
141        first one was inspected. This change makes PCRE more compatible with Perl.
142    
143    16. Unicode character properties were updated from Unicode 6.3.0.
144    
145    17. The compile-time code for auto-possessification has been refactored, based
146        on a patch by Zoltan Herczeg. It now happens after instead of during
147        compilation. The code is cleaner, and more cases are handled. The option
148        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
149        options in pcretest are provided to set it. It can also be set by
150        (*NO_AUTO_POSSESS) at the start of a pattern.
151    
152    18. The character VT has been added to the default ("C" locale) set of
153        characters that match \s and are generally treated as white space,
154        following this same change in Perl 5.18. There is now no difference between
155        "Perl space" and "POSIX space". Whether VT is treated as white space in
156        other locales depends on the locale.
157    
158    19. The code for checking named groups as conditions, either for being set or
159        for being recursed, has been refactored (this is related to 14 and 15
160        above). Processing unduplicated named groups should now be as fast at
161        numerical groups, and processing duplicated groups should be faster than
162        before.
163    
164    20. Two patches to the CMake build system, by Alexander Barkov:
165    
166          (1) Replace the "source" command by "." in CMakeLists.txt because
167              "source" is a bash-ism.
168    
169          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
170              without these the CMake build does not work on Solaris.
171    
172    21. Perl has changed its handling of \8 and \9. If there is no previously
173        encountered capturing group of those numbers, they are treated as the
174        literal characters 8 and 9 instead of a binary zero followed by the
175        literals. PCRE now does the same.
176    
177    22. Following Perl, added \o{} to specify codepoints in octal, making it
178        possible to specify values greater than 0777 and also making them
179        unambiguous.
180    
181    23. Perl now gives an error for missing closing braces after \x{... instead of
182        treating the string as literal. PCRE now does the same.
183    
184    24. RunTest used to grumble if an inappropriate test was selected explicitly,
185        but just skip it when running all tests. This make it awkward to run ranges
186        of tests when one of them was inappropriate. Now it just skips any
187        inappropriate tests, as it always did when running all tests.
188    
189    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
190        character types such as \d or \w, too many callouts were inserted, and the
191        data that they returned was rubbish.
192    
193    26. In UCP mode, \s was not matching two of the characters that Perl matches,
194        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
195        were matched by \h. The code has now been refactored so that the lists of
196        the horizontal and vertical whitespace characters used for \h and \v (which
197        are defined only in one place) are now also used for \s.
198    
199    27. Add JIT support for the 64 bit TileGX architecture.
200        Patch by Jiong Wang (Tilera Corporation).
201    
202    28. Possessive quantifiers for classes (both explicit and automatically
203        generated) now use special opcodes instead of wrapping in ONCE brackets.
204    
205    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
206        (because it's meaningless), this was not happening when PCRE_CASELESS was
207        set. Not wrong, but inefficient.
208    
209    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
210        properties for \w, \d, etc) is present in a test regex. Otherwise if the
211        test contains no characters greater than 255, Perl doesn't realise it
212        should be using Unicode semantics.
213    
214    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
215        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
216        does in Unicode mode.
217    
218    32. Added the "forbid" facility to pcretest so that putting tests into the
219        wrong test files can sometimes be quickly detected.
220    
221    33. There is now a limit (default 250) on the depth of nesting of parentheses.
222        This limit is imposed to control the amount of system stack used at compile
223        time. It can be changed at build time by --with-parens-nest-limit=xxx or
224        the equivalent in CMake.
225    
226    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
227        errors. Perl warns for these when in warning mode, but PCRE has no facility
228        for giving warnings.
229    
230    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
231        However, this was not working for (?!) because it is optimized to (*FAIL),
232        for which PCRE does not allow quantifiers. The optimization is now disabled
233        when a quantifier follows (?!). I can't see any use for this, but it makes
234        things uniform.
235    
236    36. Perl no longer allows group names to start with digits, so I have made this
237        change also in PCRE. It simplifies the code a bit.
238    
239    37. In extended mode, Perl ignores spaces before a + that indicates a
240        possessive quantifier. PCRE allowed a space before the quantifier, but not
241        before the possessive +. It now does.
242    
243    38. The use of \K (reset reported match start) within a repeated possessive
244        group such as (a\Kb)*+ was not working.
245    
246    40. Document that the same character tables must be used at compile time and
247        run time, and that the facility to pass tables to pcre_exec() and
248        pcre_dfa_exec() is for use only with saved/restored patterns.
249    
250    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
251        features for Builds with MSVC:
252    
253        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
254           builds). The .rc files can be used to set FileDescription and many other
255           attributes.
256    
257        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
258           This allows higher-level build scripts which want .pdb files to avoid
259           hard-coding the exact files needed."
260    
261    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
262        mean "start of word" and "end of word", respectively, as a transition aid.
263    
264    43. A minimizing repeat of a class containing codepoints greater than 255 in
265        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
266        compiled to use the heap for recursion.
267    
268    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
269        is configured.
270    
271    
272    Version 8.33 28-May-2013
273    ------------------------
274    
275    1.  Added 'U' to some constants that are compared to unsigned integers, to
276        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
277        variables that are added to signed variables, to ensure the result is
278        signed and can be negated.
279    
280    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
281        CMake config files.
282    
283    3.  Revise the creation of config.h.generic so that all boolean macros are
284        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
285        overriding via -D on the command line possible.
286    
287    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
288        to unsigned int is reported to make a quite noticeable speed difference in
289        a specific Windows environment. Testing on Linux did also appear to show
290        some benefit (and it is clearly not harmful). Also fixed the definition of
291        Xop which should be unsigned.
292    
293    5.  Related to (4), changing the definition of the intermediate variable cc
294        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
295        improvements.
296    
297    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
298        unnecessary spaces.
299    
300    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
301        and later.
302    
303    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
304    
305    9.  Optimizing fast_forward_start_bits in JIT.
306    
307    10. Adding support for callouts in JIT, and fixing some issues revealed
308        during this work. Namely:
309    
310        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
311    
312        (b) Minimum length was not checked before the matching is started.
313    
314    11. The value of capture_last that is passed to callouts was incorrect in some
315        cases when there was a capture on one path that was subsequently abandoned
316        after a backtrack. Also, the capture_last value is now reset after a
317        recursion, since all captures are also reset in this case.
318    
319    12. The interpreter no longer returns the "too many substrings" error in the
320        case when an overflowing capture is in a branch that is subsequently
321        abandoned after a backtrack.
322    
323    13. In the pathological case when an offset vector of size 2 is used, pcretest
324        now prints out the matched string after a yield of 0 or 1.
325    
326    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
327        Only supported by the JIT compiler at the moment.
328    
329    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
330    
331    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
332        offset of the starting point of the matching process, provided the offsets
333        vector is large enough.
334    
335    17. The \A escape now records a lookbehind value of 1, though its execution
336        does not actually inspect the previous character. This is to ensure that,
337        in partial multi-segment matching, at least one character from the old
338        segment is retained when a new segment is processed. Otherwise, if there
339        are no lookbehinds in the pattern, \A might match incorrectly at the start
340        of a new segment.
341    
342    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
343    
344    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
345        gives some modest performance improvement in 8-bit mode.
346    
347    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
348        be expressed in certain programming languages using Universal Character
349        Names.
350    
351    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
352        which points out that "non characters" are not "characters that may not
353        appear in Unicode strings" but rather "characters that are reserved for
354        internal use and have only local meaning".
355    
356    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
357        there was a conditional group that depended on an assertion, if the
358        assertion was false, the callout that immediately followed the alternation
359        in the condition was skipped when pcre_exec() was used for matching.
360    
361    23. Allow an explicit callout to be inserted before an assertion that is the
362        condition for a conditional group, for compatibility with automatic
363        callouts, which always insert a callout at this point.
364    
365    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
366        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
367    
368    25. (*PRUNE) is now supported by the JIT compiler.
369    
370    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
371    
372    27. Fix the case where there are two or more SKIPs with arguments that may be
373        ignored.
374    
375    28. (*SKIP) is now supported by the JIT compiler.
376    
377    29. (*THEN) is now supported by the JIT compiler.
378    
379    30. Update RunTest with additional test selector options.
380    
381    31. The way PCRE handles backtracking verbs has been changed in two ways.
382    
383        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
384        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
385        backtracking. In some cases this makes it more Perl-compatible, but Perl's
386        rather obscure rules do not always do the same thing.
387    
388        (2) Previously, backtracking verbs were confined within assertions. This is
389        no longer the case for positive assertions, except for (*ACCEPT). Again,
390        this sometimes improves Perl compatibility, and sometimes does not.
391    
392    32. A number of tests that were in test 2 because Perl did things differently
393        have been moved to test 1, because either Perl or PCRE has changed, and
394        these tests are now compatible.
395    
396    32. Backtracking control verbs are now handled in the same way in JIT and
397        interpreter.
398    
399    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
400        contained a forward subroutine reference caused a compile error.
401    
402    34. Auto-detect and optimize limited repetitions in JIT.
403    
404    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
405        blocking (*UTF) etc.
406    
407    36. In the interpreter, maximizing pattern repetitions for characters and
408        character types now use tail recursion, which reduces stack usage.
409    
410    37. The value of the max lookbehind was not correctly preserved if a compiled
411        and saved regex was reloaded on a host of different endianness.
412    
413    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
414        of the compiled pattern block, expand the flags field from 16 to 32 bits
415        because it was almost full.
416    
417    39. Try madvise first before posix_madvise.
418    
419    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
420        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
421        original change locked out all matches of empty strings. This has been
422        changed so that one match of an empty string per line is recognized.
423        Subsequent searches on the same line (for colouring or for --only-matching,
424        for example) do not recognize empty strings.
425    
426    41. Applied a user patch to fix a number of spelling mistakes in comments.
427    
428    42. Data lines longer than 65536 caused pcretest to crash.
429    
430    43. Clarified the data type for length and startoffset arguments for pcre_exec
431        and pcre_dfa_exec in the function-specific man pages, where they were
432        explicitly stated to be in bytes, never having been updated. I also added
433        some clarification to the pcreapi man page.
434    
435    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
436        a segmentation fault.
437    
438    
439    Version 8.32 30-November-2012
440    -----------------------------
441    
442    1.  Improved JIT compiler optimizations for first character search and single
443        character iterators.
444    
445    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
446        Patch by Daniel Richard G.
447    
448    3.  Single character iterator optimizations in the JIT compiler.
449    
450    4.  Improved JIT compiler optimizations for character ranges.
451    
452    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
453        Reported by Giuseppe D'Angelo.
454    
455    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
456        of a line, was being set incorrectly in cases where .* appeared inside
457        atomic brackets at the start of a pattern, or where there was a subsequent
458        *PRUNE or *SKIP.
459    
460    7.  Improved instruction cache flush for POWER/PowerPC.
461        Patch by Daniel Richard G.
462    
463    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
464        grep:
465    
466        (a) There is now no limit to the number of patterns to be matched.
467    
468        (b) An error is given if a pattern is too long.
469    
470        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
471            are now supported.
472    
473        (d) --exclude-from and --include-from (multiple use) have been added.
474    
475        (e) Exclusions and inclusions now apply to all files and directories, not
476            just to those obtained from scanning a directory recursively.
477    
478        (f) Multiple uses of -f and --file-list are now supported.
479    
480        (g) In a Windows environment, the default for -d has been changed from
481            "read" (the GNU grep default) to "skip", because otherwise the presence
482            of a directory in the file list provokes an error.
483    
484        (h) The documentation has been revised and clarified in places.
485    
486    9.  Improve the matching speed of capturing brackets.
487    
488    10. Changed the meaning of \X so that it now matches a Unicode extended
489        grapheme cluster.
490    
491    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
492        out POSIX threads when JIT support is configured.
493    
494    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
495    
496    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
497        structure could go wrong in environments where size_t is not the same size
498        as int.
499    
500    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
501        set.
502    
503    15. The EBCDIC support had decayed; later updates to the code had included
504        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
505        general tidy up of EBCDIC-related issues, and the documentation was also
506        not quite right. There is now a test that can be run on ASCII systems to
507        check some of the EBCDIC-related things (but is it not a full test).
508    
509    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
510        in a small tidy to the code.
511    
512    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
513    
514    18. If the --only-matching (-o) option in pcregrep is specified multiple
515        times, each one causes appropriate output. For example, -o1 -o2 outputs the
516        substrings matched by the 1st and 2nd capturing parentheses. A separating
517        string can be specified by --om-separator (default empty).
518    
519    19. Improving the first n character searches.
520    
521    20. Turn case lists for horizontal and vertical white space into macros so that
522        they are defined only once.
523    
524    21. This set of changes together give more compatible Unicode case-folding
525        behaviour for characters that have more than one other case when UCP
526        support is available.
527    
528        (a) The Unicode property table now has offsets into a new table of sets of
529            three or more characters that are case-equivalent. The MultiStage2.py
530            script that generates these tables (the pcre_ucd.c file) now scans
531            CaseFolding.txt instead of UnicodeData.txt for character case
532            information.
533    
534        (b) The code for adding characters or ranges of characters to a character
535            class has been abstracted into a generalized function that also handles
536            case-independence. In UTF-mode with UCP support, this uses the new data
537            to handle characters with more than one other case.
538    
539        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
540            whose other case is greater than 256 are now correctly matched
541            caselessly. Previously, the high codepoint matched the low one, but not
542            vice versa.
543    
544        (d) The processing of \h, \H, \v, and \ in character classes now makes use
545            of the new class addition function, using character lists defined as
546            macros alongside the case definitions of 20 above.
547    
548        (e) Caseless back references now work with characters that have more than
549            one other case.
550    
551        (f) General caseless matching of characters with more than one other case
552            is supported.
553    
554    22. Unicode character properties were updated from Unicode 6.2.0
555    
556    23. Improved CMake support under Windows. Patch by Daniel Richard G.
557    
558    24. Add support for 32-bit character strings, and UTF-32
559    
560    25. Major JIT compiler update (code refactoring and bugfixing).
561        Experimental Sparc 32 support is added.
562    
563    26. Applied a modified version of Daniel Richard G's patch to create
564        pcre.h.generic and config.h.generic by "make" instead of in the
565        PrepareRelease script.
566    
567    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
568        pcre_compile.c when checking for a zero character.
569    
570    28. Introducing a native interface for JIT. Through this interface, the compiled
571        machine code can be directly executed. The purpose of this interface is to
572        provide fast pattern matching, so several sanity checks are not performed.
573        However, feature tests are still performed. The new interface provides
574        1.4x speedup compared to the old one.
575    
576    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
577        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
578        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
579    
580    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
581        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
582        the "old" RFC 2279). Instead, it ended up passing a negative length to
583        pcre_exec().
584    
585    31. Add support for GCC's visibility feature to hide internal functions.
586    
587    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
588        "unknown -C option" after outputting 0 or 1.
589    
590    33. There is now support for generating a code coverage report for the test
591        suite in environments where gcc is the compiler and lcov is installed. This
592        is mainly for the benefit of the developers.
593    
594    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
595        unaddressable using valgrind annotations, allowing valgrind to detect
596        invalid memory accesses. This is mainly for the benefit of the developers.
597    
598    25. (*UTF) can now be used to start a pattern in any of the three libraries.
599    
600    26. Give configure error if --enable-cpp but no C++ compiler found.
601    
602    
603    Version 8.31 06-July-2012
604    -------------------------
605    
606    1.  Fixing a wrong JIT test case and some compiler warnings.
607    
608    2.  Removed a bashism from the RunTest script.
609    
610    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
611        to unsigned type, result still unsigned" that was given by an MS compiler
612        on encountering the code "-sizeof(xxx)".
613    
614    4.  Partial matching support is added to the JIT compiler.
615    
616    5.  Fixed several bugs concerned with partial matching of items that consist
617        of more than one character:
618    
619        (a) /^(..)\1/ did not partially match "aba" because checking references was
620            done on an "all or nothing" basis. This also applied to repeated
621            references.
622    
623        (b) \R did not give a hard partial match if \r was found at the end of the
624            subject.
625    
626        (c) \X did not give a hard partial match after matching one or more
627            characters at the end of the subject.
628    
629        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
630            a partial match for the string "\r".
631    
632        (e) When newline was set to CRLF, the metacharacter "." did not recognize
633            a partial match for a CR character at the end of the subject string.
634    
635    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
636        running pcretest, the text "(JIT)" added to the output whenever JIT is
637        actually used to run the match.
638    
639    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
640        or /S+[+] with a digit between 1 and 7.
641    
642    8.  OP_NOT now supports any UTF character not just single-byte ones.
643    
644    9.  (*MARK) control verb is now supported by the JIT compiler.
645    
646    10. The command "./RunTest list" lists the available tests without actually
647        running any of them. (Because I keep forgetting what they all are.)
648    
649    11. Add PCRE_INFO_MAXLOOKBEHIND.
650    
651    12. Applied a (slightly modified) user-supplied patch that improves performance
652        when the heap is used for recursion (compiled with --disable-stack-for-
653        recursion). Instead of malloc and free for each heap frame each time a
654        logical recursion happens, frames are retained on a chain and re-used where
655        possible. This sometimes gives as much as 30% improvement.
656    
657    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
658        call.
659    
660    14. As documented, (*COMMIT) is now confined to within a positive assertion.
661    
662    15. It is now possible to link pcretest with libedit as an alternative to
663        libreadline.
664    
665    16. (*COMMIT) control verb is now supported by the JIT compiler.
666    
667    17. The Unicode data tables have been updated to Unicode 6.1.0.
668    
669    18. Added --file-list option to pcregrep.
670    
671    19. Added binary file support to pcregrep, including the -a, --binary-files,
672        -I, and --text options.
673    
674    20. The madvise function is renamed for posix_madvise for QNX compatibility
675        reasons. Fixed by Giuseppe D'Angelo.
676    
677    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
678    
679    22. Changed the option for creating symbolic links for 16-bit man pages from
680        -s to -sf so that re-installing does not cause issues.
681    
682    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
683    
684    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
685        matches in certain environments (the workspace was not being correctly
686        retained). Also added to pcre_dfa_exec() a simple plausibility check on
687        some of the workspace data at the beginning of a restart.
688    
689    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
690        was not doing so when it should - probably a typo introduced by SVN 528
691        (change 8.10/14).
692    
693    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
694        \w+ when the character tables indicated that \x{c4} was a word character.
695        There were several related cases, all because the tests for doing a table
696        lookup were testing for characters less than 127 instead of 255.
697    
698    27. If a pattern contains capturing parentheses that are not used in a match,
699        their slots in the ovector are set to -1. For those that are higher than
700        any matched groups, this happens at the end of processing. In the case when
701        there were back references that the ovector was too small to contain
702        (causing temporary malloc'd memory to be used during matching), and the
703        highest capturing number was not used, memory off the end of the ovector
704        was incorrectly being set to -1. (It was using the size of the temporary
705        memory instead of the true size.)
706    
707    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
708        ovector size, it uses memory at the end of the block that it has got.
709    
710    29. Check for an overlong MARK name and give an error at compile time. The
711        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
712    
713    30. JIT compiler update.
714    
715    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
716        Rill for the patch.
717    
718    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
719    
720    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
721    
722    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
723        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
724        was enabled.
725    
726    35. Improve JIT code generation for greedy plus quantifier.
727    
728    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
729        1 to "aa" instead of to an empty string. The bug affected repeated groups
730        that could potentially match an empty string.
731    
732    37. Optimizing single character iterators in JIT.
733    
734    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
735        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
736        codepoints that are too big for the mode are faulted, and in a UTF mode,
737        disallowed codepoints are also faulted.
738    
739    39. If PCRE was compiled with UTF support, in three places in the DFA
740        matcher there was code that should only have been obeyed in UTF mode, but
741        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
742        processing when bytes with values greater than 127 were present. In 16-bit
743        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
744        both cases the values are those that cannot be the first data item in a UTF
745        character. The three items that might have provoked this were recursions,
746        possessively repeated groups, and atomic groups.
747    
748    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
749        and pcregrep, because some OS require shared objects to be explicitly
750        passed to ld, causing the link step to fail if they are not.
751    
752    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
753        mode, patterns that started with \h* or \R* might be incorrectly matched.
754    
755    
756    Version 8.30 04-February-2012
757    -----------------------------
758    
759    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
760        name is defined in ctype.h.
761    
762    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
763        only in quite long subpatterns.
764    
765    3.  Removed the function pcre_info(), which has been obsolete and deprecated
766        since it was replaced by pcre_fullinfo() in February 2000.
767    
768    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
769        match a (*MARK), and the match failed at the start of the subject, a
770        reference to memory before the start of the subject could occur. This bug
771        was introduced by fix 17 of release 8.21.
772    
773    5.  A reference to an unset group with zero minimum repetition was giving
774        totally wrong answers (in non-JavaScript-compatibility mode). For example,
775        /(another)?(\1?)test/ matched against "hello world test". This bug was
776        introduced in release 8.13.
777    
778    6.  Add support for 16-bit character strings (a large amount of work involving
779        many changes and refactorings).
780    
781    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
782        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
783        from a file.
784    
785    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
786        rounding is not applied in this particular case).
787    
788    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
789        if they appear, or are escaped, in patterns.
790    
791    10. Get rid of a number of -Wunused-but-set-variable warnings.
792    
793    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
794        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
795        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
796        also returns the mark "x". This bug applied to capturing parentheses,
797        non-capturing parentheses, and atomic parentheses. It also applied to some
798        assertions.
799    
800    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
801        information out of configure.ac instead of relying on pcre.h.generic, which
802        is not stored in the repository.
803    
804    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
805        -lreadline.
806    
807    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
808    
809    15. Applied Graycode's patch to put the top-level frame on the stack rather
810        than the heap when not using the stack for recursion. This gives a
811        performance improvement in many cases when recursion is not deep.
812    
813    16. Experimental code added to "pcretest -C" to output the stack frame size.
814    
815    
816    Version 8.21 12-Dec-2011
817    ------------------------
818    
819    1.  Updating the JIT compiler.
820    
821    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
822        are added as well.
823    
824    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
825        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
826        calling _pcre_jit_exec. Some extra comments are added.
827    
828    4.  (*MARK) settings inside atomic groups that do not contain any capturing
829        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
830        was introduced by change 18 for 8.20.
831    
832    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
833        ECMA-262 standard.
834    
835    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
836        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
837        This bug was probably introduced by change 9 of 8.13.
838    
839    7.  While fixing 6 above, I noticed that a number of other items were being
840        incorrectly rejected as "not fixed length". This arose partly because newer
841        opcodes had not been added to the fixed-length checking code. I have (a)
842        corrected the bug and added tests for these items, and (b) arranged for an
843        error to occur if an unknown opcode is encountered while checking for fixed
844        length instead of just assuming "not fixed length". The items that were
845        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
846        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
847        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
848    
849    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
850        being incorrectly compiled and would have given unpredicatble results.
851    
852    9.  A possessively repeated subpattern with minimum repeat count greater than
853        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
854        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
855        the first (A) could occur when it should not.
856    
857    10. Add a cast and remove a redundant test from the code.
858    
859    11. JIT should use pcre_malloc/pcre_free for allocation.
860    
861    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
862        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
863        is anything other than /usr, -L is still shown).
864    
865    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
866    
867    14. Perl does not support \N without a following name in a [] class; PCRE now
868        also gives an error.
869    
870    15. If a forward reference was repeated with an upper limit of around 2000,
871        it caused the error "internal error: overran compiling workspace". The
872        maximum number of forward references (including repeats) was limited by the
873        internal workspace, and dependent on the LINK_SIZE. The code has been
874        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
875        the default depends on LINK_SIZE. There is a new upper limit (for safety)
876        of around 200,000 forward references. While doing this, I also speeded up
877        the filling in of repeated forward references.
878    
879    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
880        incorrectly expecting the subject to contain another "a" after the start.
881    
882    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
883        in the match, the SKIP should be ignored. This was not happening; instead
884        the SKIP was being treated as NOMATCH. For patterns such as
885        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
886        tested.
887    
888    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
889        now much more compatible with Perl, in particular in cases where the result
890        is a non-match for a non-anchored pattern. For example, if
891        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
892        "m", where previously it did not return a name. A side effect of this
893        change is that for partial matches, the last encountered mark name is
894        returned, as for non matches. A number of tests that were previously not
895        Perl-compatible have been moved into the Perl-compatible test files. The
896        refactoring has had the pleasing side effect of removing one argument from
897        the match() function, thus reducing its stack requirements.
898    
899    19. If the /S+ option was used in pcretest to study a pattern using JIT,
900        subsequent uses of /S (without +) incorrectly behaved like /S+.
901    
902    21. Retrieve executable code size support for the JIT compiler and fixing
903        some warnings.
904    
905    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
906        not work when the shorter character appeared right at the end of the
907        subject string.
908    
909    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
910        systems.
911    
912    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
913        output it when the /M option is used in pcretest.
914    
915    25. The CheckMan script was not being included in the distribution. Also, added
916        an explicit "perl" to run Perl scripts from the PrepareRelease script
917        because this is reportedly needed in Windows.
918    
919    26. If study data was being save in a file and studying had not found a set of
920        "starts with" bytes for the pattern, the data written to the file (though
921        never used) was taken from uninitialized memory and so caused valgrind to
922        complain.
923    
924    27. Updated RunTest.bat as provided by Sheri Pierce.
925    
926    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
927    
928    29. Computation of memory usage for the table of capturing group names was
929        giving an unnecessarily large value.
930    
931    
932    Version 8.20 21-Oct-2011
933    ------------------------
934    
935    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
936        a POSIX class. After further experiments with Perl, which convinced me that
937        Perl has bugs and confusions, a closing square bracket is no longer allowed
938        in a POSIX name. This bug also affected patterns with classes that started
939        with full stops.
940    
941    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
942        captured substring, but while checking the failing first alternative,
943        substring 1 is temporarily captured. If the output vector supplied to
944        pcre_exec() was not big enough for this capture, the yield of the function
945        was still zero ("insufficient space for captured substrings"). This cannot
946        be totally fixed without adding another stack variable, which seems a lot
947        of expense for a edge case. However, I have improved the situation in cases
948        such as /(a)(b)x|abc/ matched against "abc", where the return code
949        indicates that fewer than the maximum number of slots in the ovector have
950        been set.
951    
952    3.  Related to (2) above: when there are more back references in a pattern than
953        slots in the output vector, pcre_exec() uses temporary memory during
954        matching, and copies in the captures as far as possible afterwards. It was
955        using the entire output vector, but this conflicts with the specification
956        that only 2/3 is used for passing back captured substrings. Now it uses
957        only the first 2/3, for compatibility. This is, of course, another edge
958        case.
959    
960    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
961        main code base, and can be used by building with --enable-jit. When this is
962        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
963        runtime --no-jit option is given.
964    
965    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
966        ovector, the return from the function was zero, implying that there were
967        other matches that did not fit. The correct "exactly full" value is now
968        returned.
969    
970    6.  If a subpattern that was called recursively or as a subroutine contained
971        (*PRUNE) or any other control that caused it to give a non-standard return,
972        invalid errors such as "Error -26 (nested recursion at the same subject
973        position)" or even infinite loops could occur.
974    
975    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
976        computing the minimum length on reaching *ACCEPT, and so ended up with the
977        wrong value of 1 rather than 0. Further investigation indicates that
978        computing a minimum subject length in the presence of *ACCEPT is difficult
979        (think back references, subroutine calls), and so I have changed the code
980        so that no minimum is registered for a pattern that contains *ACCEPT.
981    
982    8.  If (*THEN) was present in the first (true) branch of a conditional group,
983        it was not handled as intended. [But see 16 below.]
984    
985    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
986        Sheri Pierce.
987    
988    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
989        the first byte in a match must be "a".
990    
991    11. Change 17 for 8.13 increased the recursion depth for patterns like
992        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
993        pattern contains any instances of (*THEN). If it does not, the old
994        optimizations are restored. It would be nice to do this on a per-group
995        basis, but at the moment that is not feasible.
996    
997    12. In some environments, the output of pcretest -C is CRLF terminated. This
998        broke RunTest's code that checks for the link size. A single white space
999        character after the value is now allowed for.
1000    
1001    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1002        For "fr", it uses the Windows-specific input and output files.
1003    
1004    14. If (*THEN) appeared in a group that was called recursively or as a
1005        subroutine, it did not work as intended. [But see next item.]
1006    
1007    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1008        pattern fragments (but not containing any | characters). If A and B are
1009        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1010        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1011        D. In other words, Perl considers parentheses that do not contain any |
1012        characters to be part of a surrounding alternative, whereas PCRE was
1013        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1014        differently. PCRE now behaves in the same way as Perl, except in the case
1015        of subroutine/recursion calls such as (?1) which have in any case always
1016        been different (but PCRE had them first :-).
1017    
1018    16. Related to 15 above: Perl does not treat the | in a conditional group as
1019        creating alternatives. Such a group is treated in the same way as an
1020        ordinary group without any | characters when processing (*THEN). PCRE has
1021        been changed to match Perl's behaviour.
1022    
1023    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1024        RunGrepTest script failed.
1025    
1026    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1027        inevitable for groups that contain captures, but it can lead to a lot of
1028        stack use in large patterns. The old behaviour has been restored for atomic
1029        groups that do not contain any capturing parentheses.
1030    
1031    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1032        suppress the check for a minimum subject length at run time. (If it was
1033        given to pcre_exec() or pcre_dfa_exec() it did work.)
1034    
1035    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1036        fail to work when decoding hex characters in data strings in EBCDIC
1037        environments.
1038    
1039    21. It appears that in at least one Mac OS environment, the isxdigit() function
1040        is implemented as a macro that evaluates to its argument more than once,
1041        contravening the C 90 Standard (I haven't checked a later standard). There
1042        was an instance in pcretest which caused it to go wrong when processing
1043        \x{...} escapes in subject strings. The has been rewritten to avoid using
1044        things like p++ in the argument of isxdigit().
1045    
1046    
1047    Version 8.13 16-Aug-2011
1048  ------------------------  ------------------------
1049    
1050  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 1141  Version 8.13 02-Aug-2011
1141      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
1142      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1143      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
1144      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1145    
1146  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
1147      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 1232  Version 8.13 02-Aug-2011
1232      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1233      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1234      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1235      more like Perl.      more like Perl. (But see 8.20/1 above.)
1236    
1237  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1238      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 1267  Version 8.13 02-Aug-2011
1267      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
1268          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1269    
1270      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1271          PCRE is built.          PCRE is built.
1272    
1273      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 1288  Version 8.13 02-Aug-2011
1288  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1289      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
1290      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1291    
1292  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1293      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1294    
1295    
1296  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 1943  Version 7.9 11-Apr-09
1943  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1944      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1945      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1946      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1947        8.33.]
1948    
1949  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1950      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1143  Version 7.7 07-May-08 Line 2187  Version 7.7 07-May-08
2187      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2188      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2189      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2190      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2191      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2192      was subsequently set up correctly.)      was subsequently set up correctly.)
2193    

Legend:
Removed from v.657  
changed lines
  Added in v.1438

  ViewVC Help
Powered by ViewVC 1.1.5