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

Diff of /code/trunk/ChangeLog

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

revision 182 by ph10, Wed Jun 13 15:09:54 2007 UTC revision 1388 by ph10, Tue Nov 5 15:24:45 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.2 13-June-07  Version 8.34 xx-xxxx-201x
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_POSSESSIFY is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it.
90    
91    18. The character VT has been added to the set of characters that match \s and
92        are generally treated as white space, following this same change in Perl
93        5.18. There is now no difference between "Perl space" and "POSIX space".
94    
95    19. The code for checking named groups as conditions, either for being set or
96        for being recursed, has been refactored (this is related to 14 and 15
97        above). Processing unduplicated named groups should now be as fast at
98        numerical groups, and processing duplicated groups should be faster than
99        before.
100    
101    20. Two patches to the CMake build system, by Alexander Barkov:
102    
103          (1) Replace the "source" command by "." in CMakeLists.txt because
104              "source" is a bash-ism.
105    
106          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
107              without these the CMake build does not work on Solaris.
108    
109    21. Perl has changed its handling of \8 and \9. If there is no previously
110        encountered capturing group of those numbers, they are treated as the
111        literal characters 8 and 9 instead of a binary zero followed by the
112        literals. PCRE now does the same.
113    
114    22. Following Perl, added \o{} to specify codepoints in octal, making it
115        possible to specify values greater than 0777 and also making them
116        unambiguous.
117    
118    23. Perl now gives an error for missing closing braces after \x{... instead of
119        treating the string as literal. PCRE now does the same.
120    
121    24. RunTest used to grumble if an inappropriate test was selected explicitly,
122        but just skip it when running all tests. This make it awkward to run ranges
123        of tests when one of them was inappropriate. Now it just skips any
124        inappropriate tests, as it always did when running all tests.
125    
126    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
127        character types such as \d or \w, too many callouts were inserted, and the
128        data that they returned was rubbish.
129    
130    26. In UCP mode, \s was not matching two of the characters that Perl matches,
131        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
132        were matched by \h. The code has now been refactored so that the lists of
133        the horizontal and vertical whitespace characters used for \h and \v (which
134        are defined only in one place) are now also used for \s.
135    
136    27. Add JIT support for the 64 bit TileGX architecture.
137        Patch by Jiong Wang (Tilera Corporation).
138    
139    28. Possessive quantifiers for classes (both explicit and automatically
140        generated) now use special opcodes instead of wrapping in ONCE brackets.
141    
142    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
143        (because it's meaningless), this was not happening when PCRE_CASELESS was
144        set. Not wrong, but inefficient.
145    
146    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
147        properties for \w, \d, etc) is present in a test regex. Otherwise if the
148        test contains no characters greater than 255, Perl doesn't realise it
149        should be using Unicode semantics.
150    
151    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
152        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
153        does in Unicode mode.
154    
155    32. Added the "forbid" facility to pcretest so that putting tests into the
156        wrong test files can sometimes be quickly detected.
157    
158    
159    Version 8.33 28-May-2013
160    ------------------------
161    
162    1.  Added 'U' to some constants that are compared to unsigned integers, to
163        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
164        variables that are added to signed variables, to ensure the result is
165        signed and can be negated.
166    
167    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
168        CMake config files.
169    
170    3.  Revise the creation of config.h.generic so that all boolean macros are
171        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
172        overriding via -D on the command line possible.
173    
174    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
175        to unsigned int is reported to make a quite noticeable speed difference in
176        a specific Windows environment. Testing on Linux did also appear to show
177        some benefit (and it is clearly not harmful). Also fixed the definition of
178        Xop which should be unsigned.
179    
180    5.  Related to (4), changing the definition of the intermediate variable cc
181        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
182        improvements.
183    
184    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
185        unnecessary spaces.
186    
187    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
188        and later.
189    
190    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
191    
192    9.  Optimizing fast_forward_start_bits in JIT.
193    
194    10. Adding support for callouts in JIT, and fixing some issues revealed
195        during this work. Namely:
196    
197        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
198    
199        (b) Minimum length was not checked before the matching is started.
200    
201    11. The value of capture_last that is passed to callouts was incorrect in some
202        cases when there was a capture on one path that was subsequently abandoned
203        after a backtrack. Also, the capture_last value is now reset after a
204        recursion, since all captures are also reset in this case.
205    
206    12. The interpreter no longer returns the "too many substrings" error in the
207        case when an overflowing capture is in a branch that is subsequently
208        abandoned after a backtrack.
209    
210    13. In the pathological case when an offset vector of size 2 is used, pcretest
211        now prints out the matched string after a yield of 0 or 1.
212    
213    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
214        Only supported by the JIT compiler at the moment.
215    
216    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
217    
218    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
219        offset of the starting point of the matching process, provided the offsets
220        vector is large enough.
221    
222    17. The \A escape now records a lookbehind value of 1, though its execution
223        does not actually inspect the previous character. This is to ensure that,
224        in partial multi-segment matching, at least one character from the old
225        segment is retained when a new segment is processed. Otherwise, if there
226        are no lookbehinds in the pattern, \A might match incorrectly at the start
227        of a new segment.
228    
229    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
230    
231    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
232        gives some modest performance improvement in 8-bit mode.
233    
234    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
235        be expressed in certain programming languages using Universal Character
236        Names.
237    
238    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
239        which points out that "non characters" are not "characters that may not
240        appear in Unicode strings" but rather "characters that are reserved for
241        internal use and have only local meaning".
242    
243    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
244        there was a conditional group that depended on an assertion, if the
245        assertion was false, the callout that immediately followed the alternation
246        in the condition was skipped when pcre_exec() was used for matching.
247    
248    23. Allow an explicit callout to be inserted before an assertion that is the
249        condition for a conditional group, for compatibility with automatic
250        callouts, which always insert a callout at this point.
251    
252    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
253        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
254    
255    25. (*PRUNE) is now supported by the JIT compiler.
256    
257    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
258    
259    27. Fix the case where there are two or more SKIPs with arguments that may be
260        ignored.
261    
262    28. (*SKIP) is now supported by the JIT compiler.
263    
264    29. (*THEN) is now supported by the JIT compiler.
265    
266    30. Update RunTest with additional test selector options.
267    
268    31. The way PCRE handles backtracking verbs has been changed in two ways.
269    
270        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
271        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
272        backtracking. In some cases this makes it more Perl-compatible, but Perl's
273        rather obscure rules do not always do the same thing.
274    
275        (2) Previously, backtracking verbs were confined within assertions. This is
276        no longer the case for positive assertions, except for (*ACCEPT). Again,
277        this sometimes improves Perl compatibility, and sometimes does not.
278    
279    32. A number of tests that were in test 2 because Perl did things differently
280        have been moved to test 1, because either Perl or PCRE has changed, and
281        these tests are now compatible.
282    
283    32. Backtracking control verbs are now handled in the same way in JIT and
284        interpreter.
285    
286    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
287        contained a forward subroutine reference caused a compile error.
288    
289    34. Auto-detect and optimize limited repetitions in JIT.
290    
291    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
292        blocking (*UTF) etc.
293    
294    36. In the interpreter, maximizing pattern repetitions for characters and
295        character types now use tail recursion, which reduces stack usage.
296    
297    37. The value of the max lookbehind was not correctly preserved if a compiled
298        and saved regex was reloaded on a host of different endianness.
299    
300    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
301        of the compiled pattern block, expand the flags field from 16 to 32 bits
302        because it was almost full.
303    
304    39. Try madvise first before posix_madvise.
305    
306    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
307        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
308        original change locked out all matches of empty strings. This has been
309        changed so that one match of an empty string per line is recognized.
310        Subsequent searches on the same line (for colouring or for --only-matching,
311        for example) do not recognize empty strings.
312    
313    41. Applied a user patch to fix a number of spelling mistakes in comments.
314    
315    42. Data lines longer than 65536 caused pcretest to crash.
316    
317    43. Clarified the data type for length and startoffset arguments for pcre_exec
318        and pcre_dfa_exec in the function-specific man pages, where they were
319        explicitly stated to be in bytes, never having been updated. I also added
320        some clarification to the pcreapi man page.
321    
322    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
323        a segmentation fault.
324    
325    
326    Version 8.32 30-November-2012
327    -----------------------------
328    
329    1.  Improved JIT compiler optimizations for first character search and single
330        character iterators.
331    
332    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
333        Patch by Daniel Richard G.
334    
335    3.  Single character iterator optimizations in the JIT compiler.
336    
337    4.  Improved JIT compiler optimizations for character ranges.
338    
339    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
340        Reported by Giuseppe D'Angelo.
341    
342    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
343        of a line, was being set incorrectly in cases where .* appeared inside
344        atomic brackets at the start of a pattern, or where there was a subsequent
345        *PRUNE or *SKIP.
346    
347    7.  Improved instruction cache flush for POWER/PowerPC.
348        Patch by Daniel Richard G.
349    
350    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
351        grep:
352    
353        (a) There is now no limit to the number of patterns to be matched.
354    
355        (b) An error is given if a pattern is too long.
356    
357        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
358            are now supported.
359    
360        (d) --exclude-from and --include-from (multiple use) have been added.
361    
362        (e) Exclusions and inclusions now apply to all files and directories, not
363            just to those obtained from scanning a directory recursively.
364    
365        (f) Multiple uses of -f and --file-list are now supported.
366    
367        (g) In a Windows environment, the default for -d has been changed from
368            "read" (the GNU grep default) to "skip", because otherwise the presence
369            of a directory in the file list provokes an error.
370    
371        (h) The documentation has been revised and clarified in places.
372    
373    9.  Improve the matching speed of capturing brackets.
374    
375    10. Changed the meaning of \X so that it now matches a Unicode extended
376        grapheme cluster.
377    
378    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
379        out POSIX threads when JIT support is configured.
380    
381    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
382    
383    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
384        structure could go wrong in environments where size_t is not the same size
385        as int.
386    
387    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
388        set.
389    
390    15. The EBCDIC support had decayed; later updates to the code had included
391        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
392        general tidy up of EBCDIC-related issues, and the documentation was also
393        not quite right. There is now a test that can be run on ASCII systems to
394        check some of the EBCDIC-related things (but is it not a full test).
395    
396    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
397        in a small tidy to the code.
398    
399    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
400    
401    18. If the --only-matching (-o) option in pcregrep is specified multiple
402        times, each one causes appropriate output. For example, -o1 -o2 outputs the
403        substrings matched by the 1st and 2nd capturing parentheses. A separating
404        string can be specified by --om-separator (default empty).
405    
406    19. Improving the first n character searches.
407    
408    20. Turn case lists for horizontal and vertical white space into macros so that
409        they are defined only once.
410    
411    21. This set of changes together give more compatible Unicode case-folding
412        behaviour for characters that have more than one other case when UCP
413        support is available.
414    
415        (a) The Unicode property table now has offsets into a new table of sets of
416            three or more characters that are case-equivalent. The MultiStage2.py
417            script that generates these tables (the pcre_ucd.c file) now scans
418            CaseFolding.txt instead of UnicodeData.txt for character case
419            information.
420    
421        (b) The code for adding characters or ranges of characters to a character
422            class has been abstracted into a generalized function that also handles
423            case-independence. In UTF-mode with UCP support, this uses the new data
424            to handle characters with more than one other case.
425    
426        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
427            whose other case is greater than 256 are now correctly matched
428            caselessly. Previously, the high codepoint matched the low one, but not
429            vice versa.
430    
431        (d) The processing of \h, \H, \v, and \ in character classes now makes use
432            of the new class addition function, using character lists defined as
433            macros alongside the case definitions of 20 above.
434    
435        (e) Caseless back references now work with characters that have more than
436            one other case.
437    
438        (f) General caseless matching of characters with more than one other case
439            is supported.
440    
441    22. Unicode character properties were updated from Unicode 6.2.0
442    
443    23. Improved CMake support under Windows. Patch by Daniel Richard G.
444    
445    24. Add support for 32-bit character strings, and UTF-32
446    
447    25. Major JIT compiler update (code refactoring and bugfixing).
448        Experimental Sparc 32 support is added.
449    
450    26. Applied a modified version of Daniel Richard G's patch to create
451        pcre.h.generic and config.h.generic by "make" instead of in the
452        PrepareRelease script.
453    
454    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
455        pcre_compile.c when checking for a zero character.
456    
457    28. Introducing a native interface for JIT. Through this interface, the compiled
458        machine code can be directly executed. The purpose of this interface is to
459        provide fast pattern matching, so several sanity checks are not performed.
460        However, feature tests are still performed. The new interface provides
461        1.4x speedup compared to the old one.
462    
463    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
464        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
465        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
466    
467    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
468        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
469        the "old" RFC 2279). Instead, it ended up passing a negative length to
470        pcre_exec().
471    
472    31. Add support for GCC's visibility feature to hide internal functions.
473    
474    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
475        "unknown -C option" after outputting 0 or 1.
476    
477    33. There is now support for generating a code coverage report for the test
478        suite in environments where gcc is the compiler and lcov is installed. This
479        is mainly for the benefit of the developers.
480    
481    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
482        unaddressable using valgrind annotations, allowing valgrind to detect
483        invalid memory accesses. This is mainly for the benefit of the developers.
484    
485    25. (*UTF) can now be used to start a pattern in any of the three libraries.
486    
487    26. Give configure error if --enable-cpp but no C++ compiler found.
488    
489    
490    Version 8.31 06-July-2012
491    -------------------------
492    
493    1.  Fixing a wrong JIT test case and some compiler warnings.
494    
495    2.  Removed a bashism from the RunTest script.
496    
497    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
498        to unsigned type, result still unsigned" that was given by an MS compiler
499        on encountering the code "-sizeof(xxx)".
500    
501    4.  Partial matching support is added to the JIT compiler.
502    
503    5.  Fixed several bugs concerned with partial matching of items that consist
504        of more than one character:
505    
506        (a) /^(..)\1/ did not partially match "aba" because checking references was
507            done on an "all or nothing" basis. This also applied to repeated
508            references.
509    
510        (b) \R did not give a hard partial match if \r was found at the end of the
511            subject.
512    
513        (c) \X did not give a hard partial match after matching one or more
514            characters at the end of the subject.
515    
516        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
517            a partial match for the string "\r".
518    
519        (e) When newline was set to CRLF, the metacharacter "." did not recognize
520            a partial match for a CR character at the end of the subject string.
521    
522    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
523        running pcretest, the text "(JIT)" added to the output whenever JIT is
524        actually used to run the match.
525    
526    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
527        or /S+[+] with a digit between 1 and 7.
528    
529    8.  OP_NOT now supports any UTF character not just single-byte ones.
530    
531    9.  (*MARK) control verb is now supported by the JIT compiler.
532    
533    10. The command "./RunTest list" lists the available tests without actually
534        running any of them. (Because I keep forgetting what they all are.)
535    
536    11. Add PCRE_INFO_MAXLOOKBEHIND.
537    
538    12. Applied a (slightly modified) user-supplied patch that improves performance
539        when the heap is used for recursion (compiled with --disable-stack-for-
540        recursion). Instead of malloc and free for each heap frame each time a
541        logical recursion happens, frames are retained on a chain and re-used where
542        possible. This sometimes gives as much as 30% improvement.
543    
544    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
545        call.
546    
547    14. As documented, (*COMMIT) is now confined to within a positive assertion.
548    
549    15. It is now possible to link pcretest with libedit as an alternative to
550        libreadline.
551    
552    16. (*COMMIT) control verb is now supported by the JIT compiler.
553    
554    17. The Unicode data tables have been updated to Unicode 6.1.0.
555    
556    18. Added --file-list option to pcregrep.
557    
558    19. Added binary file support to pcregrep, including the -a, --binary-files,
559        -I, and --text options.
560    
561    20. The madvise function is renamed for posix_madvise for QNX compatibility
562        reasons. Fixed by Giuseppe D'Angelo.
563    
564    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
565    
566    22. Changed the option for creating symbolic links for 16-bit man pages from
567        -s to -sf so that re-installing does not cause issues.
568    
569    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
570    
571    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
572        matches in certain environments (the workspace was not being correctly
573        retained). Also added to pcre_dfa_exec() a simple plausibility check on
574        some of the workspace data at the beginning of a restart.
575    
576    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
577        was not doing so when it should - probably a typo introduced by SVN 528
578        (change 8.10/14).
579    
580    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
581        \w+ when the character tables indicated that \x{c4} was a word character.
582        There were several related cases, all because the tests for doing a table
583        lookup were testing for characters less than 127 instead of 255.
584    
585    27. If a pattern contains capturing parentheses that are not used in a match,
586        their slots in the ovector are set to -1. For those that are higher than
587        any matched groups, this happens at the end of processing. In the case when
588        there were back references that the ovector was too small to contain
589        (causing temporary malloc'd memory to be used during matching), and the
590        highest capturing number was not used, memory off the end of the ovector
591        was incorrectly being set to -1. (It was using the size of the temporary
592        memory instead of the true size.)
593    
594    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
595        ovector size, it uses memory at the end of the block that it has got.
596    
597    29. Check for an overlong MARK name and give an error at compile time. The
598        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
599    
600    30. JIT compiler update.
601    
602    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
603        Rill for the patch.
604    
605    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
606    
607    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
608    
609    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
610        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
611        was enabled.
612    
613    35. Improve JIT code generation for greedy plus quantifier.
614    
615    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
616        1 to "aa" instead of to an empty string. The bug affected repeated groups
617        that could potentially match an empty string.
618    
619    37. Optimizing single character iterators in JIT.
620    
621    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
622        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
623        codepoints that are too big for the mode are faulted, and in a UTF mode,
624        disallowed codepoints are also faulted.
625    
626    39. If PCRE was compiled with UTF support, in three places in the DFA
627        matcher there was code that should only have been obeyed in UTF mode, but
628        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
629        processing when bytes with values greater than 127 were present. In 16-bit
630        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
631        both cases the values are those that cannot be the first data item in a UTF
632        character. The three items that might have provoked this were recursions,
633        possessively repeated groups, and atomic groups.
634    
635    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
636        and pcregrep, because some OS require shared objects to be explicitly
637        passed to ld, causing the link step to fail if they are not.
638    
639    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
640        mode, patterns that started with \h* or \R* might be incorrectly matched.
641    
642    
643    Version 8.30 04-February-2012
644    -----------------------------
645    
646    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
647        name is defined in ctype.h.
648    
649    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
650        only in quite long subpatterns.
651    
652    3.  Removed the function pcre_info(), which has been obsolete and deprecated
653        since it was replaced by pcre_fullinfo() in February 2000.
654    
655    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
656        match a (*MARK), and the match failed at the start of the subject, a
657        reference to memory before the start of the subject could occur. This bug
658        was introduced by fix 17 of release 8.21.
659    
660    5.  A reference to an unset group with zero minimum repetition was giving
661        totally wrong answers (in non-JavaScript-compatibility mode). For example,
662        /(another)?(\1?)test/ matched against "hello world test". This bug was
663        introduced in release 8.13.
664    
665    6.  Add support for 16-bit character strings (a large amount of work involving
666        many changes and refactorings).
667    
668    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
669        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
670        from a file.
671    
672    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
673        rounding is not applied in this particular case).
674    
675    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
676        if they appear, or are escaped, in patterns.
677    
678    10. Get rid of a number of -Wunused-but-set-variable warnings.
679    
680    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
681        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
682        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
683        also returns the mark "x". This bug applied to capturing parentheses,
684        non-capturing parentheses, and atomic parentheses. It also applied to some
685        assertions.
686    
687    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
688        information out of configure.ac instead of relying on pcre.h.generic, which
689        is not stored in the repository.
690    
691    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
692        -lreadline.
693    
694    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
695    
696    15. Applied Graycode's patch to put the top-level frame on the stack rather
697        than the heap when not using the stack for recursion. This gives a
698        performance improvement in many cases when recursion is not deep.
699    
700    16. Experimental code added to "pcretest -C" to output the stack frame size.
701    
702    
703    Version 8.21 12-Dec-2011
704    ------------------------
705    
706    1.  Updating the JIT compiler.
707    
708    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
709        are added as well.
710    
711    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
712        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
713        calling _pcre_jit_exec. Some extra comments are added.
714    
715    4.  (*MARK) settings inside atomic groups that do not contain any capturing
716        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
717        was introduced by change 18 for 8.20.
718    
719    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
720        ECMA-262 standard.
721    
722    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
723        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
724        This bug was probably introduced by change 9 of 8.13.
725    
726    7.  While fixing 6 above, I noticed that a number of other items were being
727        incorrectly rejected as "not fixed length". This arose partly because newer
728        opcodes had not been added to the fixed-length checking code. I have (a)
729        corrected the bug and added tests for these items, and (b) arranged for an
730        error to occur if an unknown opcode is encountered while checking for fixed
731        length instead of just assuming "not fixed length". The items that were
732        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
733        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
734        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
735    
736    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
737        being incorrectly compiled and would have given unpredicatble results.
738    
739    9.  A possessively repeated subpattern with minimum repeat count greater than
740        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
741        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
742        the first (A) could occur when it should not.
743    
744    10. Add a cast and remove a redundant test from the code.
745    
746    11. JIT should use pcre_malloc/pcre_free for allocation.
747    
748    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
749        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
750        is anything other than /usr, -L is still shown).
751    
752    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
753    
754    14. Perl does not support \N without a following name in a [] class; PCRE now
755        also gives an error.
756    
757    15. If a forward reference was repeated with an upper limit of around 2000,
758        it caused the error "internal error: overran compiling workspace". The
759        maximum number of forward references (including repeats) was limited by the
760        internal workspace, and dependent on the LINK_SIZE. The code has been
761        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
762        the default depends on LINK_SIZE. There is a new upper limit (for safety)
763        of around 200,000 forward references. While doing this, I also speeded up
764        the filling in of repeated forward references.
765    
766    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
767        incorrectly expecting the subject to contain another "a" after the start.
768    
769    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
770        in the match, the SKIP should be ignored. This was not happening; instead
771        the SKIP was being treated as NOMATCH. For patterns such as
772        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
773        tested.
774    
775    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
776        now much more compatible with Perl, in particular in cases where the result
777        is a non-match for a non-anchored pattern. For example, if
778        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
779        "m", where previously it did not return a name. A side effect of this
780        change is that for partial matches, the last encountered mark name is
781        returned, as for non matches. A number of tests that were previously not
782        Perl-compatible have been moved into the Perl-compatible test files. The
783        refactoring has had the pleasing side effect of removing one argument from
784        the match() function, thus reducing its stack requirements.
785    
786    19. If the /S+ option was used in pcretest to study a pattern using JIT,
787        subsequent uses of /S (without +) incorrectly behaved like /S+.
788    
789    21. Retrieve executable code size support for the JIT compiler and fixing
790        some warnings.
791    
792    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
793        not work when the shorter character appeared right at the end of the
794        subject string.
795    
796    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
797        systems.
798    
799    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
800        output it when the /M option is used in pcretest.
801    
802    25. The CheckMan script was not being included in the distribution. Also, added
803        an explicit "perl" to run Perl scripts from the PrepareRelease script
804        because this is reportedly needed in Windows.
805    
806    26. If study data was being save in a file and studying had not found a set of
807        "starts with" bytes for the pattern, the data written to the file (though
808        never used) was taken from uninitialized memory and so caused valgrind to
809        complain.
810    
811    27. Updated RunTest.bat as provided by Sheri Pierce.
812    
813    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
814    
815    29. Computation of memory usage for the table of capturing group names was
816        giving an unnecessarily large value.
817    
818    
819    Version 8.20 21-Oct-2011
820    ------------------------
821    
822    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
823        a POSIX class. After further experiments with Perl, which convinced me that
824        Perl has bugs and confusions, a closing square bracket is no longer allowed
825        in a POSIX name. This bug also affected patterns with classes that started
826        with full stops.
827    
828    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
829        captured substring, but while checking the failing first alternative,
830        substring 1 is temporarily captured. If the output vector supplied to
831        pcre_exec() was not big enough for this capture, the yield of the function
832        was still zero ("insufficient space for captured substrings"). This cannot
833        be totally fixed without adding another stack variable, which seems a lot
834        of expense for a edge case. However, I have improved the situation in cases
835        such as /(a)(b)x|abc/ matched against "abc", where the return code
836        indicates that fewer than the maximum number of slots in the ovector have
837        been set.
838    
839    3.  Related to (2) above: when there are more back references in a pattern than
840        slots in the output vector, pcre_exec() uses temporary memory during
841        matching, and copies in the captures as far as possible afterwards. It was
842        using the entire output vector, but this conflicts with the specification
843        that only 2/3 is used for passing back captured substrings. Now it uses
844        only the first 2/3, for compatibility. This is, of course, another edge
845        case.
846    
847    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
848        main code base, and can be used by building with --enable-jit. When this is
849        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
850        runtime --no-jit option is given.
851    
852    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
853        ovector, the return from the function was zero, implying that there were
854        other matches that did not fit. The correct "exactly full" value is now
855        returned.
856    
857    6.  If a subpattern that was called recursively or as a subroutine contained
858        (*PRUNE) or any other control that caused it to give a non-standard return,
859        invalid errors such as "Error -26 (nested recursion at the same subject
860        position)" or even infinite loops could occur.
861    
862    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
863        computing the minimum length on reaching *ACCEPT, and so ended up with the
864        wrong value of 1 rather than 0. Further investigation indicates that
865        computing a minimum subject length in the presence of *ACCEPT is difficult
866        (think back references, subroutine calls), and so I have changed the code
867        so that no minimum is registered for a pattern that contains *ACCEPT.
868    
869    8.  If (*THEN) was present in the first (true) branch of a conditional group,
870        it was not handled as intended. [But see 16 below.]
871    
872    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
873        Sheri Pierce.
874    
875    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
876        the first byte in a match must be "a".
877    
878    11. Change 17 for 8.13 increased the recursion depth for patterns like
879        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
880        pattern contains any instances of (*THEN). If it does not, the old
881        optimizations are restored. It would be nice to do this on a per-group
882        basis, but at the moment that is not feasible.
883    
884    12. In some environments, the output of pcretest -C is CRLF terminated. This
885        broke RunTest's code that checks for the link size. A single white space
886        character after the value is now allowed for.
887    
888    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
889        For "fr", it uses the Windows-specific input and output files.
890    
891    14. If (*THEN) appeared in a group that was called recursively or as a
892        subroutine, it did not work as intended. [But see next item.]
893    
894    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
895        pattern fragments (but not containing any | characters). If A and B are
896        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
897        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
898        D. In other words, Perl considers parentheses that do not contain any |
899        characters to be part of a surrounding alternative, whereas PCRE was
900        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
901        differently. PCRE now behaves in the same way as Perl, except in the case
902        of subroutine/recursion calls such as (?1) which have in any case always
903        been different (but PCRE had them first :-).
904    
905    16. Related to 15 above: Perl does not treat the | in a conditional group as
906        creating alternatives. Such a group is treated in the same way as an
907        ordinary group without any | characters when processing (*THEN). PCRE has
908        been changed to match Perl's behaviour.
909    
910    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
911        RunGrepTest script failed.
912    
913    18. Change 22 for version 13 caused atomic groups to use more stack. This is
914        inevitable for groups that contain captures, but it can lead to a lot of
915        stack use in large patterns. The old behaviour has been restored for atomic
916        groups that do not contain any capturing parentheses.
917    
918    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
919        suppress the check for a minimum subject length at run time. (If it was
920        given to pcre_exec() or pcre_dfa_exec() it did work.)
921    
922    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
923        fail to work when decoding hex characters in data strings in EBCDIC
924        environments.
925    
926    21. It appears that in at least one Mac OS environment, the isxdigit() function
927        is implemented as a macro that evaluates to its argument more than once,
928        contravening the C 90 Standard (I haven't checked a later standard). There
929        was an instance in pcretest which caused it to go wrong when processing
930        \x{...} escapes in subject strings. The has been rewritten to avoid using
931        things like p++ in the argument of isxdigit().
932    
933    
934    Version 8.13 16-Aug-2011
935    ------------------------
936    
937    1.  The Unicode data tables have been updated to Unicode 6.0.0.
938    
939    2.  Two minor typos in pcre_internal.h have been fixed.
940    
941    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
942        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
943        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
944    
945    4.  There were a number of related bugs in the code for matching backrefences
946        caselessly in UTF-8 mode when codes for the characters concerned were
947        different numbers of bytes. For example, U+023A and U+2C65 are an upper
948        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
949        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
950        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
951        2-byte code at the end of the subject (it thought there wasn't enough data
952        left).
953    
954    5.  Comprehensive information about what went wrong is now returned by
955        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
956        as the output vector has at least 2 elements. The offset of the start of
957        the failing character and a reason code are placed in the vector.
958    
959    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
960        now returned is for the first byte of the failing character, instead of the
961        last byte inspected. This is an incompatible change, but I hope it is small
962        enough not to be a problem. It makes the returned offset consistent with
963        pcre_exec() and pcre_dfa_exec().
964    
965    7.  pcretest now gives a text phrase as well as the error number when
966        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
967        failure, the offset and reason code are output.
968    
969    8.  When \R was used with a maximizing quantifier it failed to skip backwards
970        over a \r\n pair if the subsequent match failed. Instead, it just skipped
971        back over a single character (\n). This seems wrong (because it treated the
972        two characters as a single entity when going forwards), conflicts with the
973        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
974        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
975        has been changed.
976    
977    9.  Some internal refactoring has changed the processing so that the handling
978        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
979        time (the PCRE_DOTALL option was changed this way some time ago: version
980        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
981        which was always a bit of a fudge. It also means that there is one less
982        argument for the match() function, which reduces its stack requirements
983        slightly. This change also fixes an incompatibility with Perl: the pattern
984        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
985    
986    10. More internal refactoring has drastically reduced the number of recursive
987        calls to match() for possessively repeated groups such as (abc)++ when
988        using pcre_exec().
989    
990    11. While implementing 10, a number of bugs in the handling of groups were
991        discovered and fixed:
992    
993        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
994        (a|)*(?1) gave a compile-time internal error.
995        ((a|)+)+  did not notice that the outer group could match an empty string.
996        (^a|^)+   was not marked as anchored.
997        (.*a|.*)+ was not marked as matching at start or after a newline.
998    
999    12. Yet more internal refactoring has removed another argument from the match()
1000        function. Special calls to this function are now indicated by setting a
1001        value in a variable in the "match data" data block.
1002    
1003    13. Be more explicit in pcre_study() instead of relying on "default" for
1004        opcodes that mean there is no starting character; this means that when new
1005        ones are added and accidentally left out of pcre_study(), testing should
1006        pick them up.
1007    
1008    14. The -s option of pcretest has been documented for ages as being an old
1009        synonym of -m (show memory usage). I have changed it to mean "force study
1010        for every regex", that is, assume /S for every regex. This is similar to -i
1011        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1012        using it. It makes it easier to run collections of tests with and without
1013        study enabled, and thereby test pcre_study() more easily. All the standard
1014        tests are now run with and without -s (but some patterns can be marked as
1015        "never study" - see 20 below).
1016    
1017    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1018        restoration of the capturing data to the outer values was not happening
1019        correctly.
1020    
1021    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1022        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1023        pattern had matched an empty string, and so incorrectly returned a no
1024        match.
1025    
1026    17. There was optimizing code for the last branch of non-capturing parentheses,
1027        and also for the obeyed branch of a conditional subexpression, which used
1028        tail recursion to cut down on stack usage. Unfortunately, now that there is
1029        the possibility of (*THEN) occurring in these branches, tail recursion is
1030        no longer possible because the return has to be checked for (*THEN). These
1031        two optimizations have therefore been removed. [But see 8.20/11 above.]
1032    
1033    18. If a pattern containing \R was studied, it was assumed that \R always
1034        matched two bytes, thus causing the minimum subject length to be
1035        incorrectly computed because \R can also match just one byte.
1036    
1037    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1038        was incorrectly computed.
1039    
1040    20. If /S is present twice on a test pattern in pcretest input, it now
1041        *disables* studying, thereby overriding the use of -s on the command line
1042        (see 14 above). This is necessary for one or two tests to keep the output
1043        identical in both cases.
1044    
1045    21. When (*ACCEPT) was used in an assertion that matched an empty string and
1046        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1047    
1048    22. When an atomic group that contained a capturing parenthesis was
1049        successfully matched, but the branch in which it appeared failed, the
1050        capturing was not being forgotten if a higher numbered group was later
1051        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1052        group 1 to "a", when in fact it should be unset. This applied to multi-
1053        branched capturing and non-capturing groups, repeated or not, and also to
1054        positive assertions (capturing in negative assertions does not happen
1055        in PCRE) and also to nested atomic groups.
1056    
1057    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1058        subject after a captured substring, to make it easier to tell which of a
1059        number of identical substrings has been captured.
1060    
1061    24. The way atomic groups are processed by pcre_exec() has been changed so that
1062        if they are repeated, backtracking one repetition now resets captured
1063        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1064        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1065        "aaa". Previously, it would have been "a". As part of this code
1066        refactoring, the way recursive calls are handled has also been changed.
1067    
1068    25. If an assertion condition captured any substrings, they were not passed
1069        back unless some other capturing happened later. For example, if
1070        (?(?=(a))a) was matched against "a", no capturing was returned.
1071    
1072    26. When studying a pattern that contained subroutine calls or assertions,
1073        the code for finding the minimum length of a possible match was handling
1074        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1075        group 1 called group 2 while simultaneously a separate group 2 called group
1076        1). A stack overflow occurred in this case. I have fixed this by limiting
1077        the recursion depth to 10.
1078    
1079    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1080        Fortmann. This supports explicit test numbers on the command line, and has
1081        argument validation and error reporting.
1082    
1083    28. An instance of \X with an unlimited repeat could fail if at any point the
1084        first character it looked at was a mark character.
1085    
1086    29. Some minor code refactoring concerning Unicode properties and scripts
1087        should reduce the stack requirement of match() slightly.
1088    
1089    30. Added the '=' option to pcretest to check the setting of unused capturing
1090        slots at the end of the pattern, which are documented as being -1, but are
1091        not included in the return count.
1092    
1093    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1094        compiled something random. Now it gives a compile-time error (as does
1095        Perl).
1096    
1097    32. A *MARK encountered during the processing of a positive assertion is now
1098        recorded and passed back (compatible with Perl).
1099    
1100    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1101        had alternative anchored branches, the search for a second match in a line
1102        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1103        matched the line "0102" twice. The same bug affected patterns that started
1104        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1105        twice.
1106    
1107    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1108        does, and because of capturing effects, quantifying parenthesized
1109        assertions may at times be useful. Quantifiers are now allowed for
1110        parenthesized assertions.
1111    
1112    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1113    
1114    36. \g was being checked for fancy things in a character class, when it should
1115        just be a literal "g".
1116    
1117    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1118        appearance of a nested POSIX class supersedes an apparent external class.
1119        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1120        unescaped square brackets may also appear as part of class names. For
1121        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1122        more like Perl. (But see 8.20/1 above.)
1123    
1124    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1125        was because it thought it was \N{name}, which is not supported).
1126    
1127    39. Add minix to OS list not supporting the -S option in pcretest.
1128    
1129    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1130        cannot analyze patterns in sufficient detail to catch mutual recursions
1131        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1132        subgroup is called recursively as a subpattern for a second time at the
1133        same position in the subject string. In previous releases this might have
1134        been caught by the recursion limit, or it might have run out of stack.
1135    
1136    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1137        happen only once. PCRE was, however incorrectly giving a compile time error
1138        "recursive call could loop indefinitely" because it cannot analyze the
1139        pattern in sufficient detail. The compile time test no longer happens when
1140        PCRE is compiling a conditional subpattern, but actual runaway loops are
1141        now caught at runtime (see 40 above).
1142    
1143    42. It seems that Perl allows any characters other than a closing parenthesis
1144        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1145        has been changed to be the same.
1146    
1147    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1148        as not to get warnings when autogen.sh is called. Also changed
1149        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1150    
1151    44. To help people who use pcregrep to scan files containing exceedingly long
1152        lines, the following changes have been made:
1153    
1154        (a) The default value of the buffer size parameter has been increased from
1155            8K to 20K. (The actual buffer used is three times this size.)
1156    
1157        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1158            PCRE is built.
1159    
1160        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1161            to be set at run time.
1162    
1163        (d) Numerical values in pcregrep options can be followed by K or M, for
1164            example --buffer-size=50K.
1165    
1166        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1167            given and the return code is set to 2.
1168    
1169    45. Add a pointer to the latest mark to the callout data block.
1170    
1171    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1172        partial match of an empty string instead of no match. This was specific to
1173        the use of ".".
1174    
1175    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1176        complete match instead of a partial match. This bug was dependent on both
1177        the PCRE_UTF8 and PCRE_DOTALL options being set.
1178    
1179    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1180        starting byte set, because \b was not being ignored.
1181    
1182    
1183    Version 8.12 15-Jan-2011
1184    ------------------------
1185    
1186    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1187        checks for such things as part of the documentation building process.
1188    
1189    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1190        --match-limit and --recursion-limit options (added for 8.11). In
1191        particular, this made one of the standard tests fail. (The integer value
1192        went into the wrong half of a long int.)
1193    
1194    3.  If the --colour option was given to pcregrep with -v (invert match), it
1195        did strange things, either producing crazy output, or crashing. It should,
1196        of course, ignore a request for colour when reporting lines that do not
1197        match.
1198    
1199    4.  Another pcregrep bug caused similar problems if --colour was specified with
1200        -M (multiline) and the pattern match finished with a line ending.
1201    
1202    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1203        matched in multiline mode, the following line was shown as part of the
1204        match. This seems wrong, so I have changed it.
1205    
1206    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1207        the check for further matches in the same line (so they could be coloured)
1208        to overrun the end of the current line. If another match was found, it was
1209        incorrectly shown (and then shown again when found in the next line).
1210    
1211    7.  If pcregrep was compiled under Windows, there was a reference to the
1212        function pcregrep_exit() before it was defined. I am assuming this was
1213        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1214        reported by a user. I've moved the definition above the reference.
1215    
1216    
1217    Version 8.11 10-Dec-2010
1218    ------------------------
1219    
1220    1.  (*THEN) was not working properly if there were untried alternatives prior
1221        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1222        backtracked to try for "b" instead of moving to the next alternative branch
1223        at the same level (in this case, to look for "c"). The Perl documentation
1224        is clear that when (*THEN) is backtracked onto, it goes to the "next
1225        alternative in the innermost enclosing group".
1226    
1227    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1228        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1229        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1230        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1231        (*THEN).
1232    
1233    3.  If \s appeared in a character class, it removed the VT character from
1234        the class, even if it had been included by some previous item, for example
1235        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1236        of \s, but is part of the POSIX "space" class.)
1237    
1238    4.  A partial match never returns an empty string (because you can always
1239        match an empty string at the end of the subject); however the checking for
1240        an empty string was starting at the "start of match" point. This has been
1241        changed to the "earliest inspected character" point, because the returned
1242        data for a partial match starts at this character. This means that, for
1243        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1244        (previously it gave "no match").
1245    
1246    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1247        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1248        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1249        has an implication that the given string is incomplete (because a partial
1250        match is preferred over a full match). For this reason, these items now
1251        give a partial match in this situation. [Aside: previously, the one case
1252        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1253        match rather than a full match, which was wrong by the old rules, but is
1254        now correct.]
1255    
1256    6.  There was a bug in the handling of #-introduced comments, recognized when
1257        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1258        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1259        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1260        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1261        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1262        places in pcre_compile().
1263    
1264    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1265        comments when looking ahead for named forward references to subpatterns,
1266        the only newline sequence it recognized was NL. It now handles newlines
1267        according to the set newline convention.
1268    
1269    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1270        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1271        cater for a lack of strerror(). These oversights have been fixed.
1272    
1273    9.  Added --match-limit and --recursion-limit to pcregrep.
1274    
1275    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1276    
1277    11. When the -o option was used, pcregrep was setting a return code of 1, even
1278        when matches were found, and --line-buffered was not being honoured.
1279    
1280    12. Added an optional parentheses number to the -o and --only-matching options
1281        of pcregrep.
1282    
1283    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1284        can match an empty string. The code to do it in pcretest and pcredemo
1285        needed fixing:
1286    
1287        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1288            only one byte after an empty string match just before CRLF (this case
1289            just got forgotten; "any" and "anycrlf" were OK).
1290    
1291        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1292            mode when an empty string match preceded an ASCII character followed by
1293            a non-ASCII character. (The code for advancing by one character rather
1294            than one byte was nonsense.)
1295    
1296        (c) The pcredemo.c sample program did not have any code at all to handle
1297            the cases when CRLF is a valid newline sequence.
1298    
1299    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1300        as a starting offset was within the subject string. There is now a new
1301        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1302        negative or greater than the length of the string. In order to test this,
1303        pcretest is extended to allow the setting of negative starting offsets.
1304    
1305    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1306        starting offset points to the beginning of a UTF-8 character was
1307        unnecessarily clumsy. I tidied it up.
1308    
1309    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1310        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1311    
1312    17. Nobody had reported that the --include_dir option, which was added in
1313        release 7.7 should have been called --include-dir (hyphen, not underscore)
1314        for compatibility with GNU grep. I have changed it to --include-dir, but
1315        left --include_dir as an undocumented synonym, and the same for
1316        --exclude-dir, though that is not available in GNU grep, at least as of
1317        release 2.5.4.
1318    
1319    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1320        characters from a string of bytes) have been redefined so as not to use
1321        loops, in order to improve performance in some environments. At the same
1322        time, I abstracted some of the common code into auxiliary macros to save
1323        repetition (this should not affect the compiled code).
1324    
1325    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1326        compile-time error is now given if \c is not followed by an ASCII
1327        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1328        different, and any byte value is allowed.)
1329    
1330    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1331        START_OPTIMIZE option, which is now allowed at compile time - but just
1332        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1333        to pcregrep and other applications that have no direct access to PCRE
1334        options. The new /Y option in pcretest sets this option when calling
1335        pcre_compile().
1336    
1337    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1338        back references. Groups containing recursive back references were forced to
1339        be atomic by that change, but in the case of named groups, the amount of
1340        memory required was incorrectly computed, leading to "Failed: internal
1341        error: code overflow". This has been fixed.
1342    
1343    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1344        pcretest.c, to avoid build problems in some Borland environments.
1345    
1346    
1347    Version 8.10 25-Jun-2010
1348    ------------------------
1349    
1350    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1351        THEN.
1352    
1353    2.  (*ACCEPT) was not working when inside an atomic group.
1354    
1355    3.  Inside a character class, \B is treated as a literal by default, but
1356        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1357        causes the error). The code is unchanged, but I tidied the documentation.
1358    
1359    4.  Inside a character class, PCRE always treated \R and \X as literals,
1360        whereas Perl faults them if its -w option is set. I have changed PCRE so
1361        that it faults them when PCRE_EXTRA is set.
1362    
1363    5.  Added support for \N, which always matches any character other than
1364        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1365    
1366    6.  When compiling pcregrep with newer versions of gcc which may have
1367        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1368        declared with attribute warn_unused_result" were given. Just casting the
1369        result to (void) does not stop the warnings; a more elaborate fudge is
1370        needed. I've used a macro to implement this.
1371    
1372    7.  Minor change to pcretest.c to avoid a compiler warning.
1373    
1374    8.  Added four artifical Unicode properties to help with an option to make
1375        \s etc use properties (see next item). The new properties are: Xan
1376        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1377    
1378    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1379        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1380        this option. Modified pcretest to add /W to test this facility. Added
1381        REG_UCP to make it available via the POSIX interface.
1382    
1383    10. Added --line-buffered to pcregrep.
1384    
1385    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1386        studied, and the match started with a letter with a code point greater than
1387        127 whose first byte was different to the first byte of the other case of
1388        the letter, the other case of this starting letter was not recognized
1389        (#976).
1390    
1391    12. If a pattern that was studied started with a repeated Unicode property
1392        test, for example, \p{Nd}+, there was the theoretical possibility of
1393        setting up an incorrect bitmap of starting bytes, but fortunately it could
1394        not have actually happened in practice until change 8 above was made (it
1395        added property types that matched character-matching opcodes).
1396    
1397    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1398        possible starting bytes for non-anchored patterns.
1399    
1400    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1401        \R, and also a number of cases that involve Unicode properties, both
1402        explicit and implicit when PCRE_UCP is set.
1403    
1404    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1405        input, it could crash or give wrong results if characters with values
1406        greater than 0xc0 were present in the subject string. (Detail: it assumed
1407        UTF-8 input when processing these items.)
1408    
1409    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1410        size_t is 64-bit (#991).
1411    
1412    17. Added a check for running out of memory when PCRE is compiled with
1413        --disable-stack-for-recursion (#990).
1414    
1415    18. If the last data line in a file for pcretest does not have a newline on
1416        the end, a newline was missing in the output.
1417    
1418    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1419        less than 128) in its various bitmaps. However, there is a facility for
1420        generating tables according to the current locale when PCRE is compiled. It
1421        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1422        characters, are recognized by isspace() and therefore were getting set in
1423        these tables, and indeed these tables seem to approximate to ISO 8859. This
1424        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1425        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1426        which of course cannot start UTF-8 characters. I have changed the code so
1427        that only real ASCII characters (less than 128) and the correct starting
1428        bytes for UTF-8 encodings are set for characters greater than 127 when in
1429        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1430        altogether.)
1431    
1432    20. Added the /T option to pcretest so as to be able to run tests with non-
1433        standard character tables, thus making it possible to include the tests
1434        used for 19 above in the standard set of tests.
1435    
1436    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1437        reference to a subpattern the other side of a comment that contains an
1438        opening parenthesis caused either an internal compiling error, or a
1439        reference to the wrong subpattern.
1440    
1441    
1442    Version 8.02 19-Mar-2010
1443    ------------------------
1444    
1445    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1446    
1447    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1448        configured.
1449    
1450    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1451        original author of that file, following a query about its status.
1452    
1453    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1454        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1455    
1456    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1457        quantifier applied to a forward-referencing subroutine call, could compile
1458        incorrect code or give the error "internal error: previously-checked
1459        referenced subpattern not found".
1460    
1461    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1462        variables to point to external functions. For these systems, therefore,
1463        pcre_malloc etc. are now initialized to local functions that call the
1464        relevant global functions.
1465    
1466    7.  There were two entries missing in the vectors called coptable and poptable
1467        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1468        I've fixed the data, and added a kludgy way of testing at compile time that
1469        the lengths are correct (equal to the number of opcodes).
1470    
1471    8.  Following on from 7, I added a similar kludge to check the length of the
1472        eint vector in pcreposix.c.
1473    
1474    9.  Error texts for pcre_compile() are held as one long string to avoid too
1475        much relocation at load time. To find a text, the string is searched,
1476        counting zeros. There was no check for running off the end of the string,
1477        which could happen if a new error number was added without updating the
1478        string.
1479    
1480    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1481    
1482    11. \K was not working if it appeared in an atomic group or in a group that
1483        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1484        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1485        the assertion is positive, but not if it is negative.
1486    
1487    12. Change 11 fortuitously reduced the size of the stack frame used in the
1488        "match()" function of pcre_exec.c by one pointer. Forthcoming
1489        implementation of support for (*MARK) will need an extra pointer on the
1490        stack; I have reserved it now, so that the stack frame size does not
1491        decrease.
1492    
1493    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1494        item in branch that calls a recursion is a subroutine call - as in the
1495        second branch in the above example - was incorrectly given the compile-
1496        time error "recursive call could loop indefinitely" because pcre_compile()
1497        was not correctly checking the subroutine for matching a non-empty string.
1498    
1499    14. The checks for overrunning compiling workspace could trigger after an
1500        overrun had occurred. This is a "should never occur" error, but it can be
1501        triggered by pathological patterns such as hundreds of nested parentheses.
1502        The checks now trigger 100 bytes before the end of the workspace.
1503    
1504    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1505    
1506    
1507    Version 8.01 19-Jan-2010
1508    ------------------------
1509    
1510    1.  If a pattern contained a conditional subpattern with only one branch (in
1511        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1512        computed the wrong minimum data length (which is of course zero for such
1513        subpatterns). This could cause incorrect "no match" results.
1514    
1515    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1516        the pattern is reset in the first branch, pcre_compile() failed with
1517        "internal error: code overflow at offset...". This happened only when
1518        the reset was to the original external option setting. (An optimization
1519        abstracts leading options settings into an external setting, which was the
1520        cause of this.)
1521    
1522    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1523        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1524        assertion pattern did not match (meaning that the assertion was true), it
1525        was incorrectly treated as false if the SKIP had been reached during the
1526        matching. This also applied to assertions used as conditions.
1527    
1528    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1529        assertion subpattern, including such a pattern used as a condition,
1530        unpredictable results occurred, instead of the error return
1531        PCRE_ERROR_DFA_UITEM.
1532    
1533    5.  The C++ GlobalReplace function was not working like Perl for the special
1534        situation when an empty string is matched. It now does the fancy magic
1535        stuff that is necessary.
1536    
1537    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1538        removed. (These were left over from very, very early versions of PCRE.)
1539    
1540    7.  Some cosmetic changes to the code to make life easier when compiling it
1541        as part of something else:
1542    
1543        (a) Change DEBUG to PCRE_DEBUG.
1544    
1545        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1546            called "current" as "current_branch", to prevent a collision with the
1547            Linux macro when compiled as a kernel module.
1548    
1549        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1550            prevent a collision with the Linux macro when compiled as a kernel
1551            module.
1552    
1553    8.  In pcre_compile() there are some checks for integer overflows that used to
1554        cast potentially large values to (double). This has been changed to that
1555        when building, a check for int64_t is made, and if it is found, it is used
1556        instead, thus avoiding the use of floating point arithmetic. (There is no
1557        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1558        double.
1559    
1560    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1561        2005 (difference between two addresses compared to an unsigned value).
1562    
1563    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1564        custom one, because of the following reported problem in Windows:
1565    
1566          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1567              under Win32.
1568          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1569              therefore missing the function definition.
1570          - The compiler thus generates a "C" signature for the test function.
1571          - The linker fails to find the "C" function.
1572          - PCRE fails to configure if asked to do so against libbz2.
1573    
1574    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1575        messages were output:
1576    
1577          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1578          rerunning libtoolize, to keep the correct libtool macros in-tree.
1579          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1580    
1581        I have done both of these things.
1582    
1583    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1584        most of the time, it *can* run out if it is given a pattern that contains a
1585        runaway infinite recursion. I updated the discussion in the pcrestack man
1586        page.
1587    
1588    13. Now that we have gone to the x.xx style of version numbers, the minor
1589        version may start with zero. Using 08 or 09 is a bad idea because users
1590        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1591        interpreted as invalid octal numbers. I've updated the previous comment in
1592        configure.ac, and also added a check that gives an error if 08 or 09 are
1593        used.
1594    
1595    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1596        causing partial matching to fail when the end of the subject matched \W
1597        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1598    
1599    15. There were some discrepancies between the declarations in pcre_internal.h
1600        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1601        their definitions. The declarations used "const uschar *" and the
1602        definitions used USPTR. Even though USPTR is normally defined as "const
1603        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1604        reported that: "This difference in casting confuses some C++ compilers, for
1605        example, SunCC recognizes above declarations as different functions and
1606        generates broken code for hbpcre." I have changed the declarations to use
1607        USPTR.
1608    
1609    16. GNU libtool is named differently on some systems. The autogen.sh script now
1610        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1611        (FreeBSD).
1612    
1613    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1614        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1615        comment: "Figure out how to create a longlong from a string: strtoll and
1616        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1617        instance, but it only takes 2 args instead of 3!"
1618    
1619    18. A subtle bug concerned with back references has been fixed by a change of
1620        specification, with a corresponding code fix. A pattern such as
1621        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1622        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1623        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1624        same bug. Such groups have to be quantified to be useful, or contained
1625        inside another quantified group. (If there's no repetition, the reference
1626        can never match.) The problem arises because, having left the group and
1627        moved on to the rest of the pattern, a later failure that backtracks into
1628        the group uses the captured value from the final iteration of the group
1629        rather than the correct earlier one. I have fixed this in PCRE by forcing
1630        any group that contains a reference to itself to be an atomic group; that
1631        is, there cannot be any backtracking into it once it has completed. This is
1632        similar to recursive and subroutine calls.
1633    
1634    
1635    Version 8.00 19-Oct-09
1636    ----------------------
1637    
1638    1.  The table for translating pcre_compile() error codes into POSIX error codes
1639        was out-of-date, and there was no check on the pcre_compile() error code
1640        being within the table. This could lead to an OK return being given in
1641        error.
1642    
1643    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1644        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1645        in a Windows environment.
1646    
1647    3.  The pcregrep --count option prints the count for each file even when it is
1648        zero, as does GNU grep. However, pcregrep was also printing all files when
1649        --files-with-matches was added. Now, when both options are given, it prints
1650        counts only for those files that have at least one match. (GNU grep just
1651        prints the file name in this circumstance, but including the count seems
1652        more useful - otherwise, why use --count?) Also ensured that the
1653        combination -clh just lists non-zero counts, with no names.
1654    
1655    4.  The long form of the pcregrep -F option was incorrectly implemented as
1656        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1657        but it seems right to fix it, and I didn't think it was worth preserving
1658        the old behaviour.
1659    
1660    5.  The command line items --regex=pattern and --regexp=pattern were not
1661        recognized by pcregrep, which required --regex pattern or --regexp pattern
1662        (with a space rather than an '='). The man page documented the '=' forms,
1663        which are compatible with GNU grep; these now work.
1664    
1665    6.  No libpcreposix.pc file was created for pkg-config; there was just
1666        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1667    
1668    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1669        when UCP support is not needed, by modifying the Python script that
1670        generates it from Unicode data files. This should not matter if the module
1671        is correctly used as a library, but I received one complaint about 50K of
1672        unwanted data. My guess is that the person linked everything into his
1673        program rather than using a library. Anyway, it does no harm.
1674    
1675    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1676        was a minimum greater than 1 for a wide character in a possessive
1677        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1678        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1679        character. Chaos in the form of incorrect output or a compiling loop could
1680        result.
1681    
1682    9.  The restrictions on what a pattern can contain when partial matching is
1683        requested for pcre_exec() have been removed. All patterns can now be
1684        partially matched by this function. In addition, if there are at least two
1685        slots in the offset vector, the offset of the earliest inspected character
1686        for the match and the offset of the end of the subject are set in them when
1687        PCRE_ERROR_PARTIAL is returned.
1688    
1689    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1690        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1691        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1692        and may be more useful for multi-segment matching.
1693    
1694    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1695        used to be given if ever the end of the subject was reached; now it is
1696        given only if matching could not proceed because another character was
1697        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1698        string "Z", which now yields "no match" instead of "partial match". In the
1699        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1700        final character ended with (*FAIL).
1701    
1702    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1703        if the pattern had a "must contain" character that was already found in the
1704        earlier partial match, unless partial matching was again requested. For
1705        example, with the pattern /dog.(body)?/, the "must contain" character is
1706        "g". If the first part-match was for the string "dog", restarting with
1707        "sbody" failed. This bug has been fixed.
1708    
1709    13. The string returned by pcre_dfa_exec() after a partial match has been
1710        changed so that it starts at the first inspected character rather than the
1711        first character of the match. This makes a difference only if the pattern
1712        starts with a lookbehind assertion or \b or \B (\K is not supported by
1713        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1714        matching functions compatible, and I think it's the right thing to do.
1715    
1716    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1717        so that the demonstration program is easily available in environments where
1718        PCRE has not been installed from source.
1719    
1720    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1721        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1722        library.
1723    
1724    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1725        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1726        is not the first non-POSIX option to be added. Clearly some people find
1727        these options useful.
1728    
1729    17. If a caller to the POSIX matching function regexec() passes a non-zero
1730        value for nmatch with a NULL value for pmatch, the value of
1731        nmatch is forced to zero.
1732    
1733    18. RunGrepTest did not have a test for the availability of the -u option of
1734        the diff command, as RunTest does. It now checks in the same way as
1735        RunTest, and also checks for the -b option.
1736    
1737    19. If an odd number of negated classes containing just a single character
1738        interposed, within parentheses, between a forward reference to a named
1739        subpattern and the definition of the subpattern, compilation crashed with
1740        an internal error, complaining that it could not find the referenced
1741        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1742        [The bug was that it was starting one character too far in when skipping
1743        over the character class, thus treating the ] as data rather than
1744        terminating the class. This meant it could skip too much.]
1745    
1746    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1747        /g option in pcretest when the pattern contains \K, which makes it possible
1748        to have an empty string match not at the start, even when the pattern is
1749        anchored. Updated pcretest and pcredemo to use this option.
1750    
1751    21. If the maximum number of capturing subpatterns in a recursion was greater
1752        than the maximum at the outer level, the higher number was returned, but
1753        with unset values at the outer level. The correct (outer level) value is
1754        now given.
1755    
1756    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1757        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1758        make it do so. The string so far is captured, making this feature
1759        compatible with Perl.
1760    
1761    23. The tests have been re-organized, adding tests 11 and 12, to make it
1762        possible to check the Perl 5.10 features against Perl 5.10.
1763    
1764    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1765        pattern matches a fixed length string. PCRE did not allow this; now it
1766        does. Neither allows recursion.
1767    
1768    25. I finally figured out how to implement a request to provide the minimum
1769        length of subject string that was needed in order to match a given pattern.
1770        (It was back references and recursion that I had previously got hung up
1771        on.) This code has now been added to pcre_study(); it finds a lower bound
1772        to the length of subject needed. It is not necessarily the greatest lower
1773        bound, but using it to avoid searching strings that are too short does give
1774        some useful speed-ups. The value is available to calling programs via
1775        pcre_fullinfo().
1776    
1777    26. While implementing 25, I discovered to my embarrassment that pcretest had
1778        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1779        study optimizations had never been tested with that matching function.
1780        Oops. What is worse, even when it was passed study data, there was a bug in
1781        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1782        were also very few tests of studied patterns with pcre_dfa_exec().
1783    
1784    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1785        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1786        on the other side of the coin, they are no longer allowed to have different
1787        names, because these cannot be distinguished in PCRE, and this has caused
1788        confusion. (This is a difference from Perl.)
1789    
1790    28. When duplicate subpattern names are present (necessarily with different
1791        numbers, as required by 27 above), and a test is made by name in a
1792        conditional pattern, either for a subpattern having been matched, or for
1793        recursion in such a pattern, all the associated numbered subpatterns are
1794        tested, and the overall condition is true if the condition is true for any
1795        one of them. This is the way Perl works, and is also more like the way
1796        testing by number works.
1797    
1798    
1799    Version 7.9 11-Apr-09
1800    ---------------------
1801    
1802    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1803        (pcretest), all targets were linked against these libraries. This included
1804        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1805        libraries. This caused unwanted dependencies to be created. This problem
1806        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1807        pcretest is linked with readline.
1808    
1809    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1810        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1811        moved outside it again, because FALSE and TRUE are already defined in AIX,
1812        but BOOL is not.
1813    
1814    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1815        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1816    
1817    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1818        hyphens) following file names and line numbers when outputting matching
1819        lines. This is not true; no spaces are inserted. I have also clarified the
1820        wording for the --colour (or --color) option.
1821    
1822    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1823        was not coloured; this is different to GNU grep, so I have changed it to be
1824        the same.
1825    
1826    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1827        each matching line was coloured. Now it goes on to look for further matches
1828        of any of the test patterns, which is the same behaviour as GNU grep.
1829    
1830    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1831        doesn't make sense to accept an empty string match in pcregrep, so I have
1832        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1833        seems to be how GNU grep behaves. [But see later change 40 for release
1834        8.33.]
1835    
1836    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1837        start or after a newline", because the conditional assertion was not being
1838        correctly handled. The rule now is that both the assertion and what follows
1839        in the first alternative must satisfy the test.
1840    
1841    9.  If auto-callout was enabled in a pattern with a conditional group whose
1842        condition was an assertion, PCRE could crash during matching, both with
1843        pcre_exec() and pcre_dfa_exec().
1844    
1845    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1846        used for matching.
1847    
1848    11. Unicode property support in character classes was not working for
1849        characters (bytes) greater than 127 when not in UTF-8 mode.
1850    
1851    12. Added the -M command line option to pcretest.
1852    
1853    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1854    
1855    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1856    
1857    16. Added comments and documentation about mis-use of no_arg in the C++
1858        wrapper.
1859    
1860    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1861        from Martin Jerabek that uses macro names for all relevant character and
1862        string constants.
1863    
1864    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1865        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1866        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1867        these, but not everybody uses configure.
1868    
1869    19. A conditional group that had only one branch was not being correctly
1870        recognized as an item that could match an empty string. This meant that an
1871        enclosing group might also not be so recognized, causing infinite looping
1872        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1873        with the subject "ab", where knowledge that the repeated group can match
1874        nothing is needed in order to break the loop.
1875    
1876    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1877        exec(), but without supplying a callout function, matching went wrong.
1878    
1879    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1880        leak if the size of the offset vector was greater than 30. When the vector
1881        is smaller, the saved offsets during recursion go onto a local stack
1882        vector, but for larger vectors malloc() is used. It was failing to free
1883        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1884        error, in fact).
1885    
1886    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1887        heapframe that is used only when UTF-8 support is enabled. This caused no
1888        problem, but was untidy.
1889    
1890    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1891        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1892        included within another project.
1893    
1894    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1895        slightly modified by me:
1896    
1897          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1898              not building pcregrep.
1899    
1900          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1901              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1902    
1903    25. Forward references, both numeric and by name, in patterns that made use of
1904        duplicate group numbers, could behave incorrectly or give incorrect errors,
1905        because when scanning forward to find the reference group, PCRE was not
1906        taking into account the duplicate group numbers. A pattern such as
1907        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1908    
1909    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1910        the feature of a custom pointer more persuasive (as requested by a user).
1911    
1912    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1913        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1914        pre-defined.
1915    
1916    28. Added support for (*UTF8) at the start of a pattern.
1917    
1918    29. Arrange for flags added by the "release type" setting in CMake to be shown
1919        in the configuration summary.
1920    
1921    
1922    Version 7.8 05-Sep-08
1923    ---------------------
1924    
1925    1.  Replaced UCP searching code with optimized version as implemented for Ad
1926        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1927        stage table and inline lookup instead of a function, giving speed ups of 2
1928        to 5 times on some simple patterns that I tested. Permission was given to
1929        distribute the MultiStage2.py script that generates the tables (it's not in
1930        the tarball, but is in the Subversion repository).
1931    
1932    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1933        scripts.
1934    
1935    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1936        a group with a zero qualifier. The result of the study could be incorrect,
1937        or the function might crash, depending on the pattern.
1938    
1939    4.  Caseless matching was not working for non-ASCII characters in back
1940        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1941        It now works when Unicode Property Support is available.
1942    
1943    5.  In pcretest, an escape such as \x{de} in the data was always generating
1944        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1945        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1946        truncation.
1947    
1948    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1949    
1950    7.  Added two (int) casts to pcregrep when printing the difference of two
1951        pointers, in case they are 64-bit values.
1952    
1953    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1954        test 2 if it fails.
1955    
1956    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1957        and a #define of that name to empty if it is not externally set. This is to
1958        allow users of MSVC to set it if necessary.
1959    
1960    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1961        the convenience functions in the pcre_get.c source file.
1962    
1963    11. An option change at the start of a pattern that had top-level alternatives
1964        could cause overwriting and/or a crash. This command provoked a crash in
1965        some environments:
1966    
1967          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1968    
1969        This potential security problem was recorded as CVE-2008-2371.
1970    
1971    12. For a pattern where the match had to start at the beginning or immediately
1972        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1973        pcre_dfa_exec() could read past the end of the passed subject if there was
1974        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1975        pcretest so that it places the subject at the end of its malloc-ed buffer.
1976    
1977    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1978        exec() might read past the end of the data buffer in UTF-8 mode.
1979    
1980    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1981        the data contained the byte 0x85 as part of a UTF-8 character within its
1982        first line. This applied both to normal and DFA matching.
1983    
1984    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1985        /^[^d]*?$/8 failed to match "abc".
1986    
1987    16. Added a missing copyright notice to pcrecpp_internal.h.
1988    
1989    17. Make it more clear in the documentation that values returned from
1990        pcre_exec() in ovector are byte offsets, not character counts.
1991    
1992    18. Tidied a few places to stop certain compilers from issuing warnings.
1993    
1994    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1995        supplied by Stefan Weber. I made a further small update for 7.8 because
1996        there is a change of source arrangements: the pcre_searchfuncs.c module is
1997        replaced by pcre_ucd.c.
1998    
1999    
2000    Version 7.7 07-May-08
2001    ---------------------
2002    
2003    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
2004        a string to a long long, pretend we don't even have a long long." This is
2005        done by checking for the strtoq, strtoll, and _strtoi64 functions.
2006    
2007    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
2008        pre-7.6 versions, which defined a global no_arg variable instead of putting
2009        it in the RE class. (See also #8 below.)
2010    
2011    3.  Remove a line of dead code, identified by coverity and reported by Nuno
2012        Lopes.
2013    
2014    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
2015    
2016        (1) The include/exclude patterns were being applied to the whole pathnames
2017            of files, instead of just to the final components.
2018    
2019        (2) If there was more than one level of directory, the subdirectories were
2020            skipped unless they satisfied the include/exclude conditions. This is
2021            inconsistent with GNU grep (and could even be seen as contrary to the
2022            pcregrep specification - which I improved to make it absolutely clear).
2023            The action now is always to scan all levels of directory, and just
2024            apply the include/exclude patterns to regular files.
2025    
2026    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
2027        --exclude_dir in the tests to avoid scanning .svn directories.
2028    
2029    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
2030        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
2031        doesn't support NULs in patterns.
2032    
2033    7.  Added some missing "const"s to declarations of static tables in
2034        pcre_compile.c and pcre_dfa_exec.c.
2035    
2036    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
2037        caused by fix #2  above. (Subsequently also a second patch to fix the
2038        first patch. And a third patch - this was a messy problem.)
2039    
2040    9.  Applied Craig's patch to remove the use of push_back().
2041    
2042    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
2043        matching function regexec().
2044    
2045    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
2046        which, however, unlike Perl's \g{...}, are subroutine calls, not back
2047        references. PCRE supports relative numbers with this syntax (I don't think
2048        Oniguruma does).
2049    
2050    12. Previously, a group with a zero repeat such as (...){0} was completely
2051        omitted from the compiled regex. However, this means that if the group
2052        was called as a subroutine from elsewhere in the pattern, things went wrong
2053        (an internal error was given). Such groups are now left in the compiled
2054        pattern, with a new opcode that causes them to be skipped at execution
2055        time.
2056    
2057    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
2058        to the way PCRE behaves:
2059    
2060        (a) A lone ] character is dis-allowed (Perl treats it as data).
2061    
2062        (b) A back reference to an unmatched subpattern matches an empty string
2063            (Perl fails the current match path).
2064    
2065        (c) A data ] in a character class must be notated as \] because if the
2066            first data character in a class is ], it defines an empty class. (In
2067            Perl it is not possible to have an empty class.) The empty class []
2068            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
2069            The negative empty class [^] matches any one character, independently
2070            of the DOTALL setting.
2071    
2072    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
2073        non-existent subpattern following a character class starting with ']' and
2074        containing () gave an internal compiling error instead of "reference to
2075        non-existent subpattern". Fortunately, when the pattern did exist, the
2076        compiled code was correct. (When scanning forwards to check for the
2077        existence of the subpattern, it was treating the data ']' as terminating
2078        the class, so got the count wrong. When actually compiling, the reference
2079        was subsequently set up correctly.)
2080    
2081    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
2082        it was being rejected as not supported by pcre_dfa_exec(), even though
2083        other assertions are supported. I have made pcre_dfa_exec() support
2084        (*FAIL).
2085    
2086    16. The implementation of 13c above involved the invention of a new opcode,
2087        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
2088        cannot be changed at match time, I realized I could make a small
2089        improvement to matching performance by compiling OP_ALLANY instead of
2090        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
2091        on the OP_ANY path.
2092    
2093    17. Compiling pcretest on Windows with readline support failed without the
2094        following two fixes: (1) Make the unistd.h include conditional on
2095        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
2096    
2097    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
2098        ncurses library to be included for pcretest when ReadLine support is
2099        requested, but also to allow for it to be overridden. This patch came from
2100        Daniel Bergström.
2101    
2102    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
2103        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
2104        any errors with the current Unicode tables. Thanks to Peter Kankowski for
2105        spotting this.
2106    
2107    
2108    Version 7.6 28-Jan-08
2109    ---------------------
2110    
2111    1.  A character class containing a very large number of characters with
2112        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
2113        overflow.
2114    
2115    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
2116        HAVE_LONG_LONG is not defined.
2117    
2118    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
2119        bring them up to date and include new features. This patch includes:
2120    
2121        - Fixed PH's badly added libz and libbz2 support.
2122        - Fixed a problem with static linking.
2123        - Added pcredemo. [But later removed - see 7 below.]
2124        - Fixed dftables problem and added an option.
2125        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
2126            HAVE_LONG_LONG.
2127        - Added readline support for pcretest.
2128        - Added an listing of the option settings after cmake has run.
2129    
2130    4.  A user submitted a patch to Makefile that makes it easy to create
2131        "pcre.dll" under mingw when using Configure/Make. I added stuff to
2132        Makefile.am that cause it to include this special target, without
2133        affecting anything else. Note that the same mingw target plus all
2134        the other distribution libraries and programs are now supported
2135        when configuring with CMake (see 6 below) instead of with
2136        Configure/Make.
2137    
2138    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
2139        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
2140        exported in the Windows port". It has not yet been confirmed that the patch
2141        solves the problem, but it does no harm.
2142    
2143    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
2144        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
2145        with CMake, and also correct the comment about stack recursion.
2146    
2147    7.  Remove the automatic building of pcredemo from the ./configure system and
2148        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
2149        of a program that users should build themselves after PCRE is installed, so
2150        building it automatically is not really right. What is more, it gave
2151        trouble in some build environments.
2152    
2153    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
2154    
2155    
2156    Version 7.5 10-Jan-08
2157    ---------------------
2158    
2159    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
2160        values in parens when parsing an RE using the C++ wrapper."
2161    
2162    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
2163        Characters greater than 255 were excluded from the class instead of being
2164        included.
2165    
2166    3.  The same bug as (2) above applied to negated POSIX classes such as
2167        [:^space:].
2168    
2169    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
2170        defined or documented. It seems to have been a typo for PCRE_STATIC, so
2171        I have changed it.
2172    
2173    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
2174        first named subpattern) and a construct such as (?&a) would reference the
2175        first named subpattern whose name started with "a" (in other words, the
2176        length check was missing). Both these problems are fixed. "Subpattern name
2177        expected" is now given for (?&) (a zero-length name), and this patch also
2178        makes it give the same error for \k'' (previously it complained that that
2179        was a reference to a non-existent subpattern).
2180    
2181    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
2182        this is right because (?- can be followed by option settings as well as by
2183        digits. I have, however, made the messages clearer.
2184    
2185    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
2186        than the number used in the conditional) now cause a compile-time error.
2187        This is actually not compatible with Perl, which accepts such patterns, but
2188        treats the conditional as always being FALSE (as PCRE used to), but it
2189        seems to me that giving a diagnostic is better.
2190    
2191    8.  Change "alphameric" to the more common word "alphanumeric" in comments
2192        and messages.
2193    
2194    9.  Fix two occurrences of "backslash" in comments that should have been
2195        "backspace".
2196    
2197    10. Remove two redundant lines of code that can never be obeyed (their function
2198        was moved elsewhere).
2199    
2200    11. The program that makes PCRE's Unicode character property table had a bug
2201        which caused it to generate incorrect table entries for sequences of
2202        characters that have the same character type, but are in different scripts.
2203        It amalgamated them into a single range, with the script of the first of
2204        them. In other words, some characters were in the wrong script. There were
2205        thirteen such cases, affecting characters in the following ranges:
2206    
2207          U+002b0 - U+002c1
2208          U+0060c - U+0060d
2209          U+0061e - U+00612
2210          U+0064b - U+0065e
2211          U+0074d - U+0076d
2212          U+01800 - U+01805
2213          U+01d00 - U+01d77
2214          U+01d9b - U+01dbf
2215          U+0200b - U+0200f
2216          U+030fc - U+030fe
2217          U+03260 - U+0327f
2218          U+0fb46 - U+0fbb1
2219          U+10450 - U+1049d
2220    
2221    12. The -o option (show only the matching part of a line) for pcregrep was not
2222        compatible with GNU grep in that, if there was more than one match in a
2223        line, it showed only the first of them. It now behaves in the same way as
2224        GNU grep.
2225    
2226    13. If the -o and -v options were combined for pcregrep, it printed a blank
2227        line for every non-matching line. GNU grep prints nothing, and pcregrep now
2228        does the same. The return code can be used to tell if there were any
2229        non-matching lines.
2230    
2231    14. Added --file-offsets and --line-offsets to pcregrep.
2232    
2233    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
2234        infinitely looping recursion. The bug was that positive lookaheads were not
2235        being skipped when checking for a possible empty match (negative lookaheads
2236        and both kinds of lookbehind were skipped).
2237    
2238    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
2239        inclusion of <windows.h> to before rather than after the definition of
2240        INVALID_FILE_ATTRIBUTES (patch from David Byron).
2241    
2242    17. Specifying a possessive quantifier with a specific limit for a Unicode
2243        character property caused pcre_compile() to compile bad code, which led at
2244        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
2245        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
2246        caused the error; without that there was no problem.
2247    
2248    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
2249    
2250    19. Added --enable-pcretest-libreadline.
2251    
2252    20. In pcrecpp.cc, the variable 'count' was incremented twice in
2253        RE::GlobalReplace(). As a result, the number of replacements returned was
2254        double what it should be. I removed one of the increments, but Craig sent a
2255        later patch that removed the other one (the right fix) and added unit tests
2256        that check the return values (which was not done before).
2257    
2258    21. Several CMake things:
2259    
2260        (1) Arranged that, when cmake is used on Unix, the libraries end up with
2261            the names libpcre and libpcreposix, not just pcre and pcreposix.
2262    
2263        (2) The above change means that pcretest and pcregrep are now correctly
2264            linked with the newly-built libraries, not previously installed ones.
2265    
2266        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
2267    
2268    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
2269        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
2270        UTF-8 newline character). The key issue is that the pattern starts .*;
2271        this means that the match must be either at the beginning, or after a
2272        newline. The bug was in the code for advancing after a failed match and
2273        checking that the new position followed a newline. It was not taking
2274        account of UTF-8 characters correctly.
2275    
2276    23. PCRE was behaving differently from Perl in the way it recognized POSIX
2277        character classes. PCRE was not treating the sequence [:...:] as a
2278        character class unless the ... were all letters. Perl, however, seems to
2279        allow any characters between [: and :], though of course it rejects as
2280        unknown any "names" that contain non-letters, because all the known class
2281        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
2282        for example, whereas PCRE did not - it did not recognize a POSIX character
2283        class. This seemed a bit dangerous, so the code has been changed to be
2284        closer to Perl. The behaviour is not identical to Perl, because PCRE will
2285        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
2286        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
2287        Perl does, and where it didn't before.
2288    
2289    24. Rewrite so as to remove the single use of %n from pcregrep because in some
2290        Windows environments %n is disabled by default.
2291    
2292    
2293    Version 7.4 21-Sep-07
2294    ---------------------
2295    
2296    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
2297        means that a class such as [\s] counted as "explicit reference to CR or
2298        LF". That isn't really right - the whole point of the change was to try to
2299        help when there was an actual mention of one of the two characters. So now
2300        the change happens only if \r or \n (or a literal CR or LF) character is
2301        encountered.
2302    
2303    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
2304        of both had grown to the point where there were only 3 bits left.
2305        Fortunately, there was spare space in the data structure, and so I have
2306        moved the internal flags into a new 16-bit field to free up more option
2307        bits.
2308    
2309    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
2310        but did not set the internal JCHANGED flag - either of these is enough to
2311        control the way the "get" function works - but the PCRE_INFO_JCHANGED
2312        facility is supposed to tell if (?J) was ever used, so now (?J) at the
2313        start sets both bits.
2314    
2315    4.  Added options (at build time, compile time, exec time) to change \R from
2316        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
2317    
2318    5.  doc/pcresyntax.html was missing from the distribution.
2319    
2320    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
2321        compatibility, even though it is no longer used.
2322    
2323    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
2324        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
2325        windows.h file is present (where different names are used). [This was
2326        reversed later after testing - see 16 below.]
2327    
2328    8.  Changed all #include <config.h> to #include "config.h". There were also
2329        some further <pcre.h> cases that I changed to "pcre.h".
2330    
2331    9.  When pcregrep was used with the --colour option, it missed the line ending
2332        sequence off the lines that it output.
2333    
2334    10. It was pointed out to me that arrays of string pointers cause lots of
2335        relocations when a shared library is dynamically loaded. A technique of
2336        using a single long string with a table of offsets can drastically reduce
2337        these. I have refactored PCRE in four places to do this. The result is
2338        dramatic:
2339    
2340          Originally:                          290
2341          After changing UCP table:            187
2342          After changing error message table:   43
2343          After changing table of "verbs"       36
2344          After changing table of Posix names   22
2345    
2346        Thanks to the folks working on Gregex for glib for this insight.
2347    
2348    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
2349        unicode-properties was also set.
2350    
2351    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
2352    
2353    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
2354        checked only for CRLF.
2355    
2356    14. Added casts to pcretest.c to avoid compiler warnings.
2357    
2358    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
2359    
2360    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
2361        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
2362        entirely. This removes changes made in 7 above.
2363    
2364    17. The CMake files have been updated, and there is now more information about
2365        building with CMake in the NON-UNIX-USE document.
2366    
2367    
2368    Version 7.3 28-Aug-07
2369    ---------------------
2370    
2371     1. In the rejigging of the build system that eventually resulted in 7.1, the
2372        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
2373        brackets there is not right, since it causes compilers to look for an
2374        installed pcre.h, not the version that is in the source that is being
2375        compiled (which of course may be different). I have changed it back to:
2376    
2377          #include "pcre.h"
2378    
2379        I have a vague recollection that the change was concerned with compiling in
2380        different directories, but in the new build system, that is taken care of
2381        by the VPATH setting the Makefile.
2382    
2383     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
2384        when the subject happened to end in the byte 0x85 (e.g. if the last
2385        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
2386        characters but of course it shouldn't be taken as a newline when it is part
2387        of another character. The bug was that, for an unlimited repeat of . in
2388        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
2389        characters when looking for a newline.
2390    
2391     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
2392    
2393     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
2394        in debug output.
2395    
2396     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
2397        long printing in the pcrecpp unittest when running under MinGW.
2398    
2399     6. ESC_K was left out of the EBCDIC table.
2400    
2401     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
2402        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
2403        limit also applies to "virtual nesting" when a pattern is recursive, and in
2404        this case 1000 isn't so big. I have been able to remove this limit at the
2405        expense of backing off one optimization in certain circumstances. Normally,
2406        when pcre_exec() would call its internal match() function recursively and
2407        immediately return the result unconditionally, it uses a "tail recursion"
2408        feature to save stack. However, when a subpattern that can match an empty
2409        string has an unlimited repetition quantifier, it no longer makes this
2410        optimization. That gives it a stack frame in which to save the data for
2411        checking that an empty string has been matched. Previously this was taken
2412        from the 1000-entry workspace that had been reserved. So now there is no
2413        explicit limit, but more stack is used.
2414    
2415     8. Applied Daniel's patches to solve problems with the import/export magic
2416        syntax that is required for Windows, and which was going wrong for the
2417        pcreposix and pcrecpp parts of the library. These were overlooked when this
2418        problem was solved for the main library.
2419    
2420     9. There were some crude static tests to avoid integer overflow when computing
2421        the size of patterns that contain repeated groups with explicit upper
2422        limits. As the maximum quantifier is 65535, the maximum group length was
2423        set at 30,000 so that the product of these two numbers did not overflow a
2424        32-bit integer. However, it turns out that people want to use groups that
2425        are longer than 30,000 bytes (though not repeat them that many times).
2426        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
2427        made it possible to implement the integer overflow checks in a much more
2428        dynamic way, which I have now done. The artificial limitation on group
2429        length has been removed - we now have only the limit on the total length of
2430        the compiled pattern, which depends on the LINK_SIZE setting.
2431    
2432    10. Fixed a bug in the documentation for get/copy named substring when
2433        duplicate names are permitted. If none of the named substrings are set, the
2434        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
2435        empty string.
2436    
2437    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
2438        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
2439        because the ] is interpreted as the first data character and the
2440        terminating ] is not found. PCRE has been made compatible with Perl in this
2441        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
2442        cause memory overwriting.
2443    
2444    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
2445        string has been matched (to stop an infinite loop). It was not recognizing
2446        a conditional subpattern that could match an empty string if that
2447        subpattern was within another subpattern. For example, it looped when
2448        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
2449        condition was not nested. This bug has been fixed.
2450    
2451    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
2452        past the start of the subject in the presence of bytes with the top bit
2453        set, for example "\x8aBCD".
2454    
2455    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
2456        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
2457    
2458    14. Optimized (?!) to (*FAIL).
2459    
2460    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
2461        This restricts code points to be within the range 0 to 0x10FFFF, excluding
2462        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
2463        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
2464        does: it's just the validity check that is more restrictive.
2465    
2466    16. Inserted checks for integer overflows during escape sequence (backslash)
2467        processing, and also fixed erroneous offset values for syntax errors during
2468        backslash processing.
2469    
2470    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
2471        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
2472    
2473    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
2474        caused an overrun.
2475    
2476    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
2477        something other than just ASCII characters) inside a group that had an
2478        unlimited repeat caused a loop at compile time (while checking to see
2479        whether the group could match an empty string).
2480    
2481    20. Debugging a pattern containing \p or \P could cause a crash. For example,
2482        [\P{Any}] did so. (Error in the code for printing property names.)
2483    
2484    21. An orphan \E inside a character class could cause a crash.
2485    
2486    22. A repeated capturing bracket such as (A)? could cause a wild memory
2487        reference during compilation.
2488    
2489    23. There are several functions in pcre_compile() that scan along a compiled
2490        expression for various reasons (e.g. to see if it's fixed length for look
2491        behind). There were bugs in these functions when a repeated \p or \P was
2492        present in the pattern. These operators have additional parameters compared
2493        with \d, etc, and these were not being taken into account when moving along
2494        the compiled data. Specifically:
2495    
2496        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
2497            length.
2498    
2499        (b) An item such as \pL+ within a repeated group could cause crashes or
2500            loops.
2501    
2502        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
2503            "reference to non-existent subpattern" error.
2504    
2505        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
2506    
2507    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
2508        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
2509    
2510    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
2511    
2512    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
2513        character were causing crashes (broken optimization).
2514    
2515    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2516        \p or \P) caused a compile-time loop.
2517    
2518    28. More problems have arisen in unanchored patterns when CRLF is a valid line
2519        break. For example, the unstudied pattern [\r\n]A does not match the string
2520        "\r\nA" because change 7.0/46 below moves the current point on by two
2521        characters after failing to match at the start. However, the pattern \nA
2522        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2523        the same is true. There doesn't seem any very clean way out of this, but
2524        what I have chosen to do makes the common cases work: PCRE now takes note
2525        of whether there can be an explicit match for \r or \n anywhere in the
2526        pattern, and if so, 7.0/46 no longer applies. As part of this change,
2527        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2528        pattern has explicit CR or LF references.
2529    
2530    29. Added (*CR) etc for changing newline setting at start of pattern.
2531    
2532    
2533    Version 7.2 19-Jun-07
2534  ---------------------  ---------------------
2535    
2536   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 69  Version 7.2 13-June-07 Line 2598  Version 7.2 13-June-07
2598        pcrecpp::RE("a*?").FullMatch("aaa") does not, and        pcrecpp::RE("a*?").FullMatch("aaa") does not, and
2599        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
2600    
2601    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
2602        it matched the wrong number of bytes.
2603    
2604    
2605  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
2606  ---------------------  ---------------------

Legend:
Removed from v.182  
changed lines
  Added in v.1388

  ViewVC Help
Powered by ViewVC 1.1.5