ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC revision 296 by ph10, Tue Jan 1 20:09:30 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.5 31-Dec-07
5    ---------------------
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
48    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
69    12. The -o option (show only the matching part of a line) for pcregrep was not
70        compatible with GNU grep in that, if there was more than one match in a
71        line, it showed only the first of them. It now behaves in the same way as
72        GNU grep.
74    13. If the -o and -v options were combined for pcregrep, it printed a blank
75        line for every non-matching line. GNU grep prints nothing, and pcregrep now
76        does the same. The return code can be used to tell if there were any
77        non-matching lines.
79    14. Added --file-offsets and --line-offsets to pcregrep.
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82        infinitely looping recursion. The bug was that positive lookaheads were not
83        being skipped when checking for a possible empty match (negative lookaheads
84        and both kinds of lookbehind were skipped).
86    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87        inclusion of <windows.h> to before rather than after the definition of
88        INVALID_FILE_ATTRIBUTES (patch from David Byron).
90    17. Specifying a possessive quantifier with a specific limit for a Unicode
91        character property caused pcre_compile() to compile bad code, which led at
92        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94        caused the error; without that there was no problem.
96    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
98    19. Added --enable-pcretest-libreadline.
100    20. In pcrecpp.cc, the variable 'count' was incremented twice in
101        RE::GlobalReplace(). As a result, the number of replacements returned was
102        double what it should be. I have removed one of the increments.
104    21. Several CMake things:
106        (1) Arranged that, when cmake is used on Unix, the libraries end up with
107            the names libpcre and libpcreposix, not just pcre and pcreposix.
109        (2) The above change means that pcretest and pcregrep are now correctly
110            linked with the newly-built libraries, not previously installed ones.
114    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
115        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
116        UTF-8 newline character). The key issue is that the pattern starts .*;
117        this means that the match must be either at the beginning, or after a
118        newline. The bug was in the code for advancing after a failed match and
119        checking that the new position followed a newline. It was not taking
120        account of UTF-8 characters correctly.
122    23. PCRE was behaving differently from Perl in the way it recognized POSIX
123        character classes. PCRE was not treating the sequence [:...:] as a
124        character class unless the ... were all letters. Perl, however, seems to
125        allow any characters between [: and :], though of course it rejects as
126        unknown any "names" that contain non-letters, because all the known class
127        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
128        for example, whereas PCRE did not - it did not recognize a POSIX character
129        class. This seemed a bit dangerous, so the code has been changed to be
130        closer to Perl. The behaviour is not identical to Perl, because PCRE will
131        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
132        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
133        Perl does, and where it didn't before.
135    24. Rewrite so as to remove the single use of %n from pcregrep because in some
136        Windows environments %n is disabled by default.
139    Version 7.4 21-Sep-07
140    ---------------------
142    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
143        means that a class such as [\s] counted as "explicit reference to CR or
144        LF". That isn't really right - the whole point of the change was to try to
145        help when there was an actual mention of one of the two characters. So now
146        the change happens only if \r or \n (or a literal CR or LF) character is
147        encountered.
149    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
150        of both had grown to the point where there were only 3 bits left.
151        Fortunately, there was spare space in the data structure, and so I have
152        moved the internal flags into a new 16-bit field to free up more option
153        bits.
155    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
156        but did not set the internal JCHANGED flag - either of these is enough to
157        control the way the "get" function works - but the PCRE_INFO_JCHANGED
158        facility is supposed to tell if (?J) was ever used, so now (?J) at the
159        start sets both bits.
161    4.  Added options (at build time, compile time, exec time) to change \R from
162        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
164    5.  doc/pcresyntax.html was missing from the distribution.
166    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
167        compatibility, even though it is no longer used.
169    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
170        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
171        windows.h file is present (where different names are used). [This was
172        reversed later after testing - see 16 below.]
174    8.  Changed all #include <config.h> to #include "config.h". There were also
175        some further <pcre.h> cases that I changed to "pcre.h".
177    9.  When pcregrep was used with the --colour option, it missed the line ending
178        sequence off the lines that it output.
180    10. It was pointed out to me that arrays of string pointers cause lots of
181        relocations when a shared library is dynamically loaded. A technique of
182        using a single long string with a table of offsets can drastically reduce
183        these. I have refactored PCRE in four places to do this. The result is
184        dramatic:
186          Originally:                          290
187          After changing UCP table:            187
188          After changing error message table:   43
189          After changing table of "verbs"       36
190          After changing table of Posix names   22
192        Thanks to the folks working on Gregex for glib for this insight.
194    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
195        unicode-properties was also set.
197    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
199    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
200        checked only for CRLF.
202    14. Added casts to pcretest.c to avoid compiler warnings.
204    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
206    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
207        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
208        entirely. This removes changes made in 7 above.
210    17. The CMake files have been updated, and there is now more information about
211        building with CMake in the NON-UNIX-USE document.
214    Version 7.3 28-Aug-07
215    ---------------------
217     1. In the rejigging of the build system that eventually resulted in 7.1, the
218        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
219        brackets there is not right, since it causes compilers to look for an
220        installed pcre.h, not the version that is in the source that is being
221        compiled (which of course may be different). I have changed it back to:
223          #include "pcre.h"
225        I have a vague recollection that the change was concerned with compiling in
226        different directories, but in the new build system, that is taken care of
227        by the VPATH setting the Makefile.
229     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
230        when the subject happened to end in the byte 0x85 (e.g. if the last
231        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
232        characters but of course it shouldn't be taken as a newline when it is part
233        of another character. The bug was that, for an unlimited repeat of . in
234        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
235        characters when looking for a newline.
237     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
239     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
240        in debug output.
242     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
243        long printing in the pcrecpp unittest when running under MinGW.
245     6. ESC_K was left out of the EBCDIC table.
247     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
248        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
249        limit also applies to "virtual nesting" when a pattern is recursive, and in
250        this case 1000 isn't so big. I have been able to remove this limit at the
251        expense of backing off one optimization in certain circumstances. Normally,
252        when pcre_exec() would call its internal match() function recursively and
253        immediately return the result unconditionally, it uses a "tail recursion"
254        feature to save stack. However, when a subpattern that can match an empty
255        string has an unlimited repetition quantifier, it no longer makes this
256        optimization. That gives it a stack frame in which to save the data for
257        checking that an empty string has been matched. Previously this was taken
258        from the 1000-entry workspace that had been reserved. So now there is no
259        explicit limit, but more stack is used.
261     8. Applied Daniel's patches to solve problems with the import/export magic
262        syntax that is required for Windows, and which was going wrong for the
263        pcreposix and pcrecpp parts of the library. These were overlooked when this
264        problem was solved for the main library.
266     9. There were some crude static tests to avoid integer overflow when computing
267        the size of patterns that contain repeated groups with explicit upper
268        limits. As the maximum quantifier is 65535, the maximum group length was
269        set at 30,000 so that the product of these two numbers did not overflow a
270        32-bit integer. However, it turns out that people want to use groups that
271        are longer than 30,000 bytes (though not repeat them that many times).
272        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
273        made it possible to implement the integer overflow checks in a much more
274        dynamic way, which I have now done. The artificial limitation on group
275        length has been removed - we now have only the limit on the total length of
276        the compiled pattern, which depends on the LINK_SIZE setting.
278    10. Fixed a bug in the documentation for get/copy named substring when
279        duplicate names are permitted. If none of the named substrings are set, the
280        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
281        empty string.
283    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
284        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
285        because the ] is interpreted as the first data character and the
286        terminating ] is not found. PCRE has been made compatible with Perl in this
287        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
288        cause memory overwriting.
290    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
291        string has been matched (to stop an infinite loop). It was not recognizing
292        a conditional subpattern that could match an empty string if that
293        subpattern was within another subpattern. For example, it looped when
294        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
295        condition was not nested. This bug has been fixed.
297    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
298        past the start of the subject in the presence of bytes with the top bit
299        set, for example "\x8aBCD".
301    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
302        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
304    14. Optimized (?!) to (*FAIL).
306    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
307        This restricts code points to be within the range 0 to 0x10FFFF, excluding
308        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
309        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
310        does: it's just the validity check that is more restrictive.
312    16. Inserted checks for integer overflows during escape sequence (backslash)
313        processing, and also fixed erroneous offset values for syntax errors during
314        backslash processing.
316    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
317        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
319    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
320        caused an overrun.
322    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
323        something other than just ASCII characters) inside a group that had an
324        unlimited repeat caused a loop at compile time (while checking to see
325        whether the group could match an empty string).
327    20. Debugging a pattern containing \p or \P could cause a crash. For example,
328        [\P{Any}] did so. (Error in the code for printing property names.)
330    21. An orphan \E inside a character class could cause a crash.
332    22. A repeated capturing bracket such as (A)? could cause a wild memory
333        reference during compilation.
335    23. There are several functions in pcre_compile() that scan along a compiled
336        expression for various reasons (e.g. to see if it's fixed length for look
337        behind). There were bugs in these functions when a repeated \p or \P was
338        present in the pattern. These operators have additional parameters compared
339        with \d, etc, and these were not being taken into account when moving along
340        the compiled data. Specifically:
342        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
343            length.
345        (b) An item such as \pL+ within a repeated group could cause crashes or
346            loops.
348        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
349            "reference to non-existent subpattern" error.
351        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
353    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
354        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
356    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
358    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
359        character were causing crashes (broken optimization).
361    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
362        \p or \P) caused a compile-time loop.
364    28. More problems have arisen in unanchored patterns when CRLF is a valid line
365        break. For example, the unstudied pattern [\r\n]A does not match the string
366        "\r\nA" because change 7.0/46 below moves the current point on by two
367        characters after failing to match at the start. However, the pattern \nA
368        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
369        the same is true. There doesn't seem any very clean way out of this, but
370        what I have chosen to do makes the common cases work: PCRE now takes note
371        of whether there can be an explicit match for \r or \n anywhere in the
372        pattern, and if so, 7.0/46 no longer applies. As part of this change,
373        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
374        pattern has explicit CR or LF references.
376    29. Added (*CR) etc for changing newline setting at start of pattern.
379    Version 7.2 19-Jun-07
380    ---------------------
382     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
383        which is apparently normally available under Windows.
385     2. Re-jig the pcregrep tests with different newline settings in an attempt
386        to make them independent of the local environment's newline setting.
388     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
390     4. Some of the "internals" tests were previously cut out when the link size
391        was not 2, because the output contained actual offsets. The recent new
392        "Z" feature of pcretest means that these can be cut out, making the tests
393        usable with all link sizes.
395     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
396        stack recursion. This gives a massive performance boost under BSD, but just
397        a small improvement under Linux. However, it saves one field in the frame
398        in all cases.
400     6. Added more features from the forthcoming Perl 5.10:
402        (a) (?-n) (where n is a string of digits) is a relative subroutine or
403            recursion call. It refers to the nth most recently opened parentheses.
405        (b) (?+n) is also a relative subroutine call; it refers to the nth next
406            to be opened parentheses.
408        (c) Conditions that refer to capturing parentheses can be specified
409            relatively, for example, (?(-2)... or (?(+3)...
411        (d) \K resets the start of the current match so that everything before
412            is not part of it.
414        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
416        (f) \g{name} is another synonym - part of Perl 5.10's unification of
417            reference syntax.
419        (g) (?| introduces a group in which the numbering of parentheses in each
420            alternative starts with the same number.
422        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
424     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
427     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
428        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
429        for detecting groups that can match an empty string.
431     9. A pattern with a very large number of alternatives (more than several
432        hundred) was running out of internal workspace during the pre-compile
433        phase, where pcre_compile() figures out how much memory will be needed. A
434        bit of new cunning has reduced the workspace needed for groups with
435        alternatives. The 1000-alternative test pattern now uses 12 bytes of
436        workspace instead of running out of the 4096 that are available.
438    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
440    11. Applied patch from Google to remove an optimization that didn't quite work.
441        The report of the bug said:
443          pcrecpp::RE("a*").FullMatch("aaa") matches, while
444          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
445          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
447    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
448        it matched the wrong number of bytes.
451    Version 7.1 24-Apr-07
452    ---------------------
454     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
455        that is more "standard", making use of automake and other Autotools. There
456        is some re-arrangement of the files and adjustment of comments consequent
457        on this.
459     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
460        for recursive directory scanning broke on some systems because the files
461        are not scanned in any specific order and on different systems the order
462        was different. A call to "sort" has been inserted into RunGrepTest for the
463        approprate test as a short-term fix. In the longer term there may be an
464        alternative.
466     3. I had an email from Eric Raymond about problems translating some of PCRE's
467        man pages to HTML (despite the fact that I distribute HTML pages, some
468        people do their own conversions for various reasons). The problems
469        concerned the use of low-level troff macros .br and .in. I have therefore
470        removed all such uses from the man pages (some were redundant, some could
471        be replaced by .nf/.fi pairs). The 132html script that I use to generate
472        HTML has been updated to handle .nf/.fi and to complain if it encounters
473        .br or .in.
475     4. Updated comments in configure.ac that get placed in config.h.in and also
476        arranged for config.h to be included in the distribution, with the name
477        config.h.generic, for the benefit of those who have to compile without
478        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
480     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
481        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
482        makevp.bat for the current PCRE, using the additional files
483        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
485     6. A Windows user reported a minor discrepancy with test 2, which turned out
486        to be caused by a trailing space on an input line that had got lost in his
487        copy. The trailing space was an accident, so I've just removed it.
489     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
490        that is needed.
492     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
493        as "const" (a) because they are and (b) because it helps the PHP
494        maintainers who have recently made a script to detect big data structures
495        in the php code that should be moved to the .rodata section. I remembered
496        to update Builducptable as well, so it won't revert if ucptable.h is ever
497        re-created.
499     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
500        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
501        order to be able to cut out the UTF-8 tables in the latter when UTF-8
502        support is not required. This saves 1.5-2K of code, which is important in
503        some applications.
505        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
506        so as not to refer to the tables, even though these functions will never be
507        called when UTF-8 support is disabled. Otherwise there are problems with a
508        shared library.
510    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
512        (a) It was defining its arguments as char * instead of void *.
514        (b) It was assuming that all moves were upwards in memory; this was true
515            a long time ago when I wrote it, but is no longer the case.
517        The emulated memove() is provided for those environments that have neither
518        memmove() nor bcopy(). I didn't think anyone used it these days, but that
519        is clearly not the case, as these two bugs were recently reported.
521    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
522        and Detrail to create the HTML documentation, the .txt form of the man
523        pages, and it removes trailing spaces from listed files. It also creates
524        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
525        case, it wraps all the #defines with #ifndefs. This script should be run
526        before "make dist".
528    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
529        with Unicode property support.
531        (a) For a maximizing quantifier, if the two different cases of the
532            character were of different lengths in their UTF-8 codings (there are
533            some cases like this - I found 11), and the matching function had to
534            back up over a mixture of the two cases, it incorrectly assumed they
535            were both the same length.
537        (b) When PCRE was configured to use the heap rather than the stack for
538            recursion during matching, it was not correctly preserving the data for
539            the other case of a UTF-8 character when checking ahead for a match
540            while processing a minimizing repeat. If the check also involved
541            matching a wide character, but failed, corruption could cause an
542            erroneous result when trying to check for a repeat of the original
543            character.
545    13. Some tidying changes to the testing mechanism:
547        (a) The RunTest script now detects the internal link size and whether there
548            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
549            values substituted by "configure". (The RunGrepTest script already did
550            this for UTF-8.) The configure.ac script no longer substitutes the
551            relevant variables.
553        (b) The debugging options /B and /D in pcretest show the compiled bytecode
554            with length and offset values. This means that the output is different
555            for different internal link sizes. Test 2 is skipped for link sizes
556            other than 2 because of this, bypassing the problem. Unfortunately,
557            there was also a test in test 3 (the locale tests) that used /B and
558            failed for link sizes other than 2. Rather than cut the whole test out,
559            I have added a new /Z option to pcretest that replaces the length and
560            offset values with spaces. This is now used to make test 3 independent
561            of link size. (Test 2 will be tidied up later.)
563    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
564        segmentation fault instead of returning the appropriate error message.
566    15. In multiline mode when the newline sequence was set to "any", the pattern
567        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
568        This doesn't seem right; it now treats the CRLF combination as the line
569        ending, and so does not match in that case. It's only a pattern such as ^$
570        that would hit this one: something like ^ABC$ would have failed after \r
571        and then tried again after \r\n.
573    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
574        in an attempt to make files that differ only in their line terminators
575        compare equal. This works on Linux.
577    17. Under certain error circumstances pcregrep might try to free random memory
578        as it exited. This is now fixed, thanks to valgrind.
580    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
581        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
582        was because its rules for how to advance for /g after matching an empty
583        string at the end of a line did not allow for this case. They now check for
584        it specially.
586    20. pcretest is supposed to handle patterns and data of any length, by
587        extending its buffers when necessary. It was getting this wrong when the
588        buffer for a data line had to be extended.
590    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
591        CRLF as a newline sequence.
593    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
594        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
595        I have nevertheless tidied it up.
597    23. Added some casts to kill warnings from HP-UX ia64 compiler.
599    24. Added a man page for pcre-config.
602    Version 7.0 19-Dec-06
603    ---------------------
605     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
606        moving to gcc 4.1.1.
608     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
609        sys/time.h, which is documented as needed for this function. It doesn't
610        seem to matter on Linux, but it showed up on some releases of OS X.
612     3. It seems that there are systems where bytes whose values are greater than
613        127 match isprint() in the "C" locale. The "C" locale should be the
614        default when a C program starts up. In most systems, only ASCII printing
615        characters match isprint(). This difference caused the output from pcretest
616        to vary, making some of the tests fail. I have changed pcretest so that:
618        (a) When it is outputting text in the compiled version of a pattern, bytes
619            other than 32-126 are always shown as hex escapes.
621        (b) When it is outputting text that is a matched part of a subject string,
622            it does the same, unless a different locale has been set for the match
623            (using the /L modifier). In this case, it uses isprint() to decide.
625     4. Fixed a major bug that caused incorrect computation of the amount of memory
626        required for a compiled pattern when options that changed within the
627        pattern affected the logic of the preliminary scan that determines the
628        length. The relevant options are -x, and -i in UTF-8 mode. The result was
629        that the computed length was too small. The symptoms of this bug were
630        either the PCRE error "internal error: code overflow" from pcre_compile(),
631        or a glibc crash with a message such as "pcretest: free(): invalid next
632        size (fast)". Examples of patterns that provoked this bug (shown in
633        pcretest format) are:
635          /(?-x: )/x
636          /(?x)(?-x: \s*#\s*)/
637          /((?i)[\x{c0}])/8
638          /(?i:[\x{c0}])/8
640        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
641        is now done differently.
643     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
644        wrapper classes; (b) implement a new function in the C++ scanner that is
645        more efficient than the old way of doing things because it avoids levels of
646        recursion in the regex matching; (c) add a paragraph to the documentation
647        for the FullMatch() function.
649     6. The escape sequence \n was being treated as whatever was defined as
650        "newline". Not only was this contrary to the documentation, which states
651        that \n is character 10 (hex 0A), but it also went horribly wrong when
652        "newline" was defined as CRLF. This has been fixed.
654     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
655        was being set to -1 for the "end of line" case (supposedly a value that no
656        character can have). Though this value is never used (the check for end of
657        line is "zero bytes in current character"), it caused compiler complaints.
658        I've changed it to 0xffffffff.
660     8. In pcre_version.c, the version string was being built by a sequence of
661        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
662        string (as it is for production releases) called a macro with an empty
663        argument. The C standard says the result of this is undefined. The gcc
664        compiler treats it as an empty string (which was what was wanted) but it is
665        reported that Visual C gives an error. The source has been hacked around to
666        avoid this problem.
668     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
669        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
670        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
671        of them did).
673    10. Originally, pcretest opened its input and output without "b"; then I was
674        told that "b" was needed in some environments, so it was added for release
675        5.0 to both the input and output. (It makes no difference on Unix-like
676        systems.) Later I was told that it is wrong for the input on Windows. I've
677        now abstracted the modes into two macros, to make it easier to fiddle with
678        them, and removed "b" from the input mode under Windows.
680    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
682    12. Added -help and --help to pcretest as an official way of being reminded
683        of the options.
685    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
686        and pcrecpp.cc because they annoy compilers at high warning levels.
688    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
690    15. Fixed an occurrence of == in configure.ac that should have been = (shell
691        scripts are not C programs :-) and which was not noticed because it works
692        on Linux.
694    16. pcretest is supposed to handle any length of pattern and data line (as one
695        line or as a continued sequence of lines) by extending its input buffer if
696        necessary. This feature was broken for very long pattern lines, leading to
697        a string of junk being passed to pcre_compile() if the pattern was longer
698        than about 50K.
700    17. I have done a major re-factoring of the way pcre_compile() computes the
701        amount of memory needed for a compiled pattern. Previously, there was code
702        that made a preliminary scan of the pattern in order to do this. That was
703        OK when PCRE was new, but as the facilities have expanded, it has become
704        harder and harder to keep it in step with the real compile phase, and there
705        have been a number of bugs (see for example, 4 above). I have now found a
706        cunning way of running the real compile function in a "fake" mode that
707        enables it to compute how much memory it would need, while actually only
708        ever using a few hundred bytes of working memory and without too many
709        tests of the mode. This should make future maintenance and development
710        easier. A side effect of this work is that the limit of 200 on the nesting
711        depth of parentheses has been removed (though this was never a serious
712        limitation, I suspect). However, there is a downside: pcre_compile() now
713        runs more slowly than before (30% or more, depending on the pattern). I
714        hope this isn't a big issue. There is no effect on runtime performance.
716    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
717        newline (only possible for the last line of a file) and it was a
718        pattern that set a locale (followed by /Lsomething), pcretest crashed.
720    19. Added additional timing features to pcretest. (1) The -tm option now times
721        matching only, not compiling. (2) Both -t and -tm can be followed, as a
722        separate command line item, by a number that specifies the number of
723        repeats to use when timing. The default is 50000; this gives better
724        precision, but takes uncomfortably long for very large patterns.
726    20. Extended pcre_study() to be more clever in cases where a branch of a
727        subpattern has no definite first character. For example, (a*|b*)[cd] would
728        previously give no result from pcre_study(). Now it recognizes that the
729        first character must be a, b, c, or d.
731    21. There was an incorrect error "recursive call could loop indefinitely" if
732        a subpattern (or the entire pattern) that was being tested for matching an
733        empty string contained only one non-empty item after a nested subpattern.
734        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
735        incorrectly, because the \d was being skipped in the check.
737    22. The pcretest program now has a new pattern option /B and a command line
738        option -b, which is equivalent to adding /B to every pattern. This causes
739        it to show the compiled bytecode, without the additional information that
740        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
741        is the same as /B/I).
743    23. A new optimization is now able automatically to treat some sequences such
744        as a*b as a*+b. More specifically, if something simple (such as a character
745        or a simple class like \d) has an unlimited quantifier, and is followed by
746        something that cannot possibly match the quantified thing, the quantifier
747        is automatically "possessified".
749    24. A recursive reference to a subpattern whose number was greater than 39
750        went wrong under certain circumstances in UTF-8 mode. This bug could also
751        have affected the operation of pcre_study().
753    25. Realized that a little bit of performance could be had by replacing
754        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
756    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
758    27. Possessive quantifiers such as a++ were previously implemented by turning
759        them into atomic groups such as ($>a+). Now they have their own opcodes,
760        which improves performance. This includes the automatically created ones
761        from 23 above.
763    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
764        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
765        the first matched character to be a colon. This applied both to named and
766        numbered groups.
768    29. The ucpinternal.h header file was missing its idempotency #ifdef.
770    30. I was sent a "project" file called libpcre.a.dev which I understand makes
771        building PCRE on Windows easier, so I have included it in the distribution.
773    31. There is now a check in pcretest against a ridiculously large number being
774        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
775        loop, the loop is abandoned.
777    32. Forward references to subpatterns in conditions such as (?(2)...) where
778        subpattern 2 is defined later cause pcre_compile() to search forwards in
779        the pattern for the relevant set of parentheses. This search went wrong
780        when there were unescaped parentheses in a character class, parentheses
781        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
783    33. "Subroutine" calls and backreferences were previously restricted to
784        referencing subpatterns earlier in the regex. This restriction has now
785        been removed.
787    34. Added a number of extra features that are going to be in Perl 5.10. On the
788        whole, these are just syntactic alternatives for features that PCRE had
789        previously implemented using the Python syntax or my own invention. The
790        other formats are all retained for compatibility.
792        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
793            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
794            also .NET compatible.
796        (b) A recursion or subroutine call to a named group can now be defined as
797            (?&name) as well as (?P>name).
799        (c) A backreference to a named group can now be defined as \k<name> or
800            \k'name' as well as (?P=name). The new forms, as well as being in Perl
801            5.10, are also .NET compatible.
803        (d) A conditional reference to a named group can now use the syntax
804            (?(<name>) or (?('name') as well as (?(name).
806        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
807            groups (named and numbered) that are never evaluated inline, but can be
808            called as "subroutines" from elsewhere. In effect, the DEFINE condition
809            is always false. There may be only one alternative in such a group.
811        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
812            as the simple (?(R). The condition is true only if the most recent
813            recursion is that of the given number or name. It does not search out
814            through the entire recursion stack.
816        (g) The escape \gN or \g{N} has been added, where N is a positive or
817            negative number, specifying an absolute or relative reference.
819    35. Tidied to get rid of some further signed/unsigned compiler warnings and
820        some "unreachable code" warnings.
822    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
823        things, this adds five new scripts.
825    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
826        There were also incompatibilities regarding the handling of \Q..\E inside
827        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
828        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
830    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
831        matches an empty string, and forcibly breaks the loop. There were bugs in
832        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
833        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
834        separate and independent bugs (that affected different cases) have been
835        fixed.
837    39. Refactored the code to abolish the use of different opcodes for small
838        capturing bracket numbers. This is a tidy that I avoided doing when I
839        removed the limit on the number of capturing brackets for 3.5 back in 2001.
840        The new approach is not only tidier, it makes it possible to reduce the
841        memory needed to fix the previous bug (38).
843    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
844        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
845        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
846        mode.
848    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
849        report.
851    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
852        copy construction and assignment in the C++ wrapper.
854    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
855        couple of bugs that could have given wrong results in the "--newline=crlf"
856        case.
858    44. Added a number of casts and did some reorganization of signed/unsigned int
859        variables following suggestions from Dair Grant. Also renamed the variable
860        "this" as "item" because it is a C++ keyword.
862    45. Arranged for dftables to add
864          #include "pcre_internal.h"
866        to pcre_chartables.c because without it, gcc 4.x may remove the array
867        definition from the final binary if PCRE is built into a static library and
868        dead code stripping is activated.
870    46. For an unanchored pattern, if a match attempt fails at the start of a
871        newline sequence, and the newline setting is CRLF or ANY, and the next two
872        characters are CRLF, advance by two characters instead of one.
875    Version 6.7 04-Jul-06
876    ---------------------
878     1. In order to handle tests when input lines are enormously long, pcretest has
879        been re-factored so that it automatically extends its buffers when
880        necessary. The code is crude, but this _is_ just a test program. The
881        default size has been increased from 32K to 50K.
883     2. The code in pcre_study() was using the value of the re argument before
884        testing it for NULL. (Of course, in any sensible call of the function, it
885        won't be NULL.)
887     3. The memmove() emulation function in pcre_internal.h, which is used on
888        systems that lack both memmove() and bcopy() - that is, hardly ever -
889        was missing a "static" storage class specifier.
891     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
892        containing an extended class (one that cannot be represented by a bitmap
893        because it contains high-valued characters or Unicode property items, e.g.
894        [\pZ]). Almost always one would set UTF-8 mode when processing such a
895        pattern, but PCRE should not loop if you do not (it no longer does).
896        [Detail: two cases were found: (a) a repeated subpattern containing an
897        extended class; (b) a recursive reference to a subpattern that followed a
898        previous extended class. It wasn't skipping over the extended class
899        correctly when UTF-8 mode was not set.]
901     5. A negated single-character class was not being recognized as fixed-length
902        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
903        compile error "lookbehind assertion is not fixed length".
905     6. The RunPerlTest auxiliary script was showing an unexpected difference
906        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
907        write a Perl script that can interpret lines of an input file either as
908        byte characters or as UTF-8, which is what "perltest" was being required to
909        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
910        can't do is switch easily at run time between having the "use utf8;" pragma
911        or not. In the end, I fudged it by using the RunPerlTest script to insert
912        "use utf8;" explicitly for the UTF-8 tests.
914     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
915        the end of the subject string, contrary to the documentation and to what
916        Perl does. This was true of both matching functions. Now it matches only at
917        the start of the subject and immediately after *internal* newlines.
919     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
920        a pointer to an int instead of a pointer to an unsigned long int. This
921        caused problems on 64-bit systems.
923     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
924        instance of the 'standard' template library not being so standard".
926    10. There was no check on the number of named subpatterns nor the maximum
927        length of a subpattern name. The product of these values is used to compute
928        the size of the memory block for a compiled pattern. By supplying a very
929        long subpattern name and a large number of named subpatterns, the size
930        computation could be caused to overflow. This is now prevented by limiting
931        the length of names to 32 characters, and the number of named subpatterns
932        to 10,000.
934    11. Subpatterns that are repeated with specific counts have to be replicated in
935        the compiled pattern. The size of memory for this was computed from the
936        length of the subpattern and the repeat count. The latter is limited to
937        65535, but there was no limit on the former, meaning that integer overflow
938        could in principle occur. The compiled length of a repeated subpattern is
939        now limited to 30,000 bytes in order to prevent this.
941    12. Added the optional facility to have named substrings with the same name.
943    13. Added the ability to use a named substring as a condition, using the
944        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
945        are numbers (not recommended). Forward references are permitted.
947    14. Added forward references in named backreferences (if you see what I mean).
949    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
950        pattern could run off the end of the subject. For example, the pattern
951        "(?s)(.{1,5})"8 did this with the subject "ab".
953    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
954        PCRE_CASELESS was set when matching characters that were quantified with ?
955        or *.
957    17. A character class other than a single negated character that had a minimum
958        but no maximum quantifier - for example [ab]{6,} - was not handled
959        correctly by pce_dfa_exec(). It would match only one character.
961    18. A valid (though odd) pattern that looked like a POSIX character
962        class but used an invalid character after [ (for example [[,abc,]]) caused
963        pcre_compile() to give the error "Failed: internal error: code overflow" or
964        in some cases to crash with a glibc free() error. This could even happen if
965        the pattern terminated after [[ but there just happened to be a sequence of
966        letters, a binary zero, and a closing ] in the memory that followed.
968    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
969        over the years. Originally (before any Unicode support), just the bottom 8
970        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
971        output from "man perlunicode" includes this:
973          The regular expression compiler produces polymorphic opcodes.  That
974          is, the pattern adapts to the data and automatically switches to
975          the Unicode character scheme when presented with Unicode data--or
976          instead uses a traditional byte scheme when presented with byte
977          data.
979        Sadly, a wide octal escape does not cause a switch, and in a string with
980        no other multibyte characters, these octal escapes are treated as before.
981        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
982        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
983        Unicode string.
985        I have not perpetrated such confusion in PCRE. Up till now, it took just
986        the bottom 8 bits, as in old Perl. I have now made octal escapes with
987        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
988        translate to the appropriate multibyte character.
990    29. Applied some refactoring to reduce the number of warnings from Microsoft
991        and Borland compilers. This has included removing the fudge introduced
992        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
993        a warning about an unused variable.
995    21. PCRE has not included VT (character 0x0b) in the set of whitespace
996        characters since release 4.0, because Perl (from release 5.004) does not.
997        [Or at least, is documented not to: some releases seem to be in conflict
998        with the documentation.] However, when a pattern was studied with
999        pcre_study() and all its branches started with \s, PCRE still included VT
1000        as a possible starting character. Of course, this did no harm; it just
1001        caused an unnecessary match attempt.
1003    22. Removed a now-redundant internal flag bit that recorded the fact that case
1004        dependency changed within the pattern. This was once needed for "required
1005        byte" processing, but is no longer used. This recovers a now-scarce options
1006        bit. Also moved the least significant internal flag bit to the most-
1007        significant bit of the word, which was not previously used (hangover from
1008        the days when it was an int rather than a uint) to free up another bit for
1009        the future.
1011    23. Added support for CRLF line endings as well as CR and LF. As well as the
1012        default being selectable at build time, it can now be changed at runtime
1013        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1014        specify that it is scanning data with non-default line endings.
1016    24. Changed the definition of CXXLINK to make it agree with the definition of
1017        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1019    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1020        recursions. This makes a big different to stack usage for some patterns.
1022    26. If a subpattern containing a named recursion or subroutine reference such
1023        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1024        the space required for the compiled pattern went wrong and gave too small a
1025        value. Depending on the environment, this could lead to "Failed: internal
1026        error: code overflow at offset 49" or "glibc detected double free or
1027        corruption" errors.
1029    27. Applied patches from Google (a) to support the new newline modes and (b) to
1030        advance over multibyte UTF-8 characters in GlobalReplace.
1032    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1033        difference for some implementation of PCRE in some Windows version.
1035    29. Added some extra testing facilities to pcretest:
1037        \q<number>   in a data line sets the "match limit" value
1038        \Q<number>   in a data line sets the "match recursion limt" value
1039        -S <number>  sets the stack size, where <number> is in megabytes
1041        The -S option isn't available for Windows.
1044    Version 6.6 06-Feb-06
1045    ---------------------
1047     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1048        in pcreposix.h. I have copied the definition from pcre.h.
1050     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1051        because pcre.h is no longer a built file.
1053     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1054        not normally included in the compiled code.
1057    Version 6.5 01-Feb-06
1058    ---------------------
1060     1. When using the partial match feature with pcre_dfa_exec(), it was not
1061        anchoring the second and subsequent partial matches at the new starting
1062        point. This could lead to incorrect results. For example, with the pattern
1063        /1234/, partially matching against "123" and then "a4" gave a match.
1065     2. Changes to pcregrep:
1067        (a) All non-match returns from pcre_exec() were being treated as failures
1068            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1069            error message is output. Some extra information is given for the
1070            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1071            probably the only errors that are likely to be caused by users (by
1072            specifying a regex that has nested indefinite repeats, for instance).
1073            If there are more than 20 of these errors, pcregrep is abandoned.
1075        (b) A binary zero was treated as data while matching, but terminated the
1076            output line if it was written out. This has been fixed: binary zeroes
1077            are now no different to any other data bytes.
1079        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1080            used to set a locale for matching. The --locale=xxxx long option has
1081            been added (no short equivalent) to specify a locale explicitly on the
1082            pcregrep command, overriding the environment variables.
1084        (d) When -B was used with -n, some line numbers in the output were one less
1085            than they should have been.
1087        (e) Added the -o (--only-matching) option.
1089        (f) If -A or -C was used with -c (count only), some lines of context were
1090            accidentally printed for the final match.
1092        (g) Added the -H (--with-filename) option.
1094        (h) The combination of options -rh failed to suppress file names for files
1095            that were found from directory arguments.
1097        (i) Added the -D (--devices) and -d (--directories) options.
1099        (j) Added the -F (--fixed-strings) option.
1101        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1103        (l) Added the --colo(u)r option.
1105        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1106            is not present by default.
1108     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1109        items such as (?R) or (?1), when the recursion could match a number of
1110        alternatives. If it matched one of the alternatives, but subsequently,
1111        outside the recursion, there was a failure, the code tried to back up into
1112        the recursion. However, because of the way PCRE is implemented, this is not
1113        possible, and the result was an incorrect result from the match.
1115        In order to prevent this happening, the specification of recursion has
1116        been changed so that all such subpatterns are automatically treated as
1117        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1119     4. I had overlooked the fact that, in some locales, there are characters for
1120        which isalpha() is true but neither isupper() nor islower() are true. In
1121        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1122        and ordfeminine) are like this. This affected the treatment of \w and \W
1123        when they appeared in character classes, but not when they appeared outside
1124        a character class. The bit map for "word" characters is now created
1125        separately from the results of isalnum() instead of just taking it from the
1126        upper, lower, and digit maps. (Plus the underscore character, of course.)
1128     5. The above bug also affected the handling of POSIX character classes such as
1129        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1130        permanent tables. Instead, the bit maps for such a class were previously
1131        created as the appropriate unions of the upper, lower, and digit bitmaps.
1132        Now they are created by subtraction from the [[:word:]] class, which has
1133        its own bitmap.
1135     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1136        It is created by subtracting the vertical space characters (\x09, \x0a,
1137        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1138        subtraction was done in the overall bitmap for a character class, meaning
1139        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1140        be recognized. This bug has been fixed.
1142     7. Patches from the folks at Google:
1144          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1145          real life, but is still worth protecting against".
1147          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1148          regular expressions".
1150          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1151          have it.
1153          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1154          "configure" and the latter not, in order to fix a problem somebody had
1155          with compiling the Arg class on HP-UX.
1157          (e) Improve the error-handling of the C++ wrapper a little bit.
1159          (f) New tests for checking recursion limiting.
1161     8. The pcre_memmove() function, which is used only if the environment does not
1162        have a standard memmove() function (and is therefore rarely compiled),
1163        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1164        returning a result (though PCRE never actually uses the result).
1166     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1167        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1168        returned instead of calling malloc() with an overflowing number that would
1169        most likely cause subsequent chaos.
1171    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1173    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1174        with this option is matched, the nmatch and pmatch options of regexec() are
1175        ignored.
1177    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1178        provided in case anyone wants to the the POSIX interface with UTF-8
1179        strings.
1181    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1182        C++ linking (needed for some HP-UX environments).
1184    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1185        (unused parameter) and in the pcre_printint() function (omitted "default"
1186        switch label when the default is to do nothing).
1188    15. Added some code to make it possible, when PCRE is compiled as a C++
1189        library, to replace subject pointers for pcre_exec() with a smart pointer
1190        class, thus making it possible to process discontinuous strings.
1192    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1193        much the same function. They were added by different people who were trying
1194        to make PCRE easy to compile on non-Unix systems. It has been suggested
1195        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1196        for compiling on Windows systems. I have therefore replaced it with
1197        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1198        defaults to "extern" for C or "extern C" for C++, which works fine on
1199        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1200        SCOPE with something explicit in config.h. In addition:
1202        (a) pcreposix.h still had just "extern" instead of either of these macros;
1203            I have replaced it with PCRE_DATA_SCOPE.
1205        (b) Functions such as _pcre_xclass(), which are internal to the library,
1206            but external in the C sense, all had PCRE_EXPORT in their definitions.
1207            This is apparently wrong for the Windows case, so I have removed it.
1208            (It makes no difference on Unix-like systems.)
1210    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1211        of recursive calls to match(). This is different to MATCH_LIMIT because
1212        that limits the total number of calls to match(), not all of which increase
1213        the depth of recursion. Limiting the recursion depth limits the amount of
1214        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1215        when PCRE is compiled, and changed at run time. A patch from Google adds
1216        this functionality to the C++ interface.
1218    18. Changes to the handling of Unicode character properties:
1220        (a) Updated the table to Unicode 4.1.0.
1222        (b) Recognize characters that are not in the table as "Cn" (undefined).
1224        (c) I revised the way the table is implemented to a much improved format
1225            which includes recognition of ranges. It now supports the ranges that
1226            are defined in UnicodeData.txt, and it also amalgamates other
1227            characters into ranges. This has reduced the number of entries in the
1228            table from around 16,000 to around 3,000, thus reducing its size
1229            considerably. I realized I did not need to use a tree structure after
1230            all - a binary chop search is just as efficient. Having reduced the
1231            number of entries, I extended their size from 6 bytes to 8 bytes to
1232            allow for more data.
1234        (d) Added support for Unicode script names via properties such as \p{Han}.
1236    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1237        matching that character.
1239    20. When matching a repeated Unicode property with a minimum greater than zero,
1240        (for example \pL{2,}), PCRE could look past the end of the subject if it
1241        reached it while seeking the minimum number of characters. This could
1242        happen only if some of the characters were more than one byte long, because
1243        there is a check for at least the minimum number of bytes.
1245    21. Refactored the implementation of \p and \P so as to be more general, to
1246        allow for more different types of property in future. This has changed the
1247        compiled form incompatibly. Anybody with saved compiled patterns that use
1248        \p or \P will have to recompile them.
1250    22. Added "Any" and "L&" to the supported property types.
1252    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1253        but give a compile time error if the value is greater than 0xff.
1255    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1256        accidentally not being installed or uninstalled.
1258    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1259        made were to insert the current release number. This seemed silly, because
1260        it made things harder for people building PCRE on systems that don't run
1261        "configure". I have turned pcre.h into a distributed file, no longer built
1262        by "configure", with the version identification directly included. There is
1263        no longer a pcre.h.in file.
1265        However, this change necessitated a change to the pcre-config script as
1266        well. It is built from pcre-config.in, and one of the substitutions was the
1267        release number. I have updated configure.ac so that ./configure now finds
1268        the release number by grepping pcre.h.
1270    26. Added the ability to run the tests under valgrind.
1273    Version 6.4 05-Sep-05
1274    ---------------------
1276     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1277        "--" to be printed when multiple files were scanned, even when none of the
1278        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1279        consider it to be a bug, and have restored the previous behaviour.
1281     2. A couple of code tidies to get rid of compiler warnings.
1283     3. The pcretest program used to cheat by referring to symbols in the library
1284        whose names begin with _pcre_. These are internal symbols that are not
1285        really supposed to be visible externally, and in some environments it is
1286        possible to suppress them. The cheating is now confined to including
1287        certain files from the library's source, which is a bit cleaner.
1289     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1290        file's purpose clearer.
1292     5. Reorganized pcre_ucp_findchar().
1295  Version 6.3 15-Aug-05  Version 6.3 15-Aug-05
1296  ---------------------  ---------------------

Removed from v.83  
changed lines
  Added in v.296

  ViewVC Help
Powered by ViewVC 1.1.5