ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 69 by nigel, Sat Feb 24 21:40:18 2007 UTC revision 307 by ph10, Sun Jan 20 20:36:45 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.6 19-Jan-08
5    ---------------------
7    1.  A character class containing a very large number of characters with
8        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
9        overflow.
11    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
12        HAVE_LONG_LONG is not defined.
14    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
15        bring them up to date and include new features. This patch includes:
17        - Fixed PH's badly added libz and libbz2 support.
18        - Fixed a problem with static linking.
19        - Added pcredemo.
20        - Fixed dftables problem and added an option.
21        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
22            HAVE_LONG_LONG.
23        - Added readline support for pcretest.
24        - Added an listing of the option settings after cmake has run.
26    4.  A user submitted a patch to Makefile that makes it easy to created a dll
27        under mingw. I added stuff to Makefile.am that cause it to include this
28        special target, without affecting anything else.
31    Version 7.5 10-Jan-08
32    ---------------------
34    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
35        values in parens when parsing an RE using the C++ wrapper."
37    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
38        Characters greater than 255 were excluded from the class instead of being
39        included.
41    3.  The same bug as (2) above applied to negated POSIX classes such as
42        [:^space:].
44    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
45        defined or documented. It seems to have been a typo for PCRE_STATIC, so
46        I have changed it.
48    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
49        first named subpattern) and a construct such as (?&a) would reference the
50        first named subpattern whose name started with "a" (in other words, the
51        length check was missing). Both these problems are fixed. "Subpattern name
52        expected" is now given for (?&) (a zero-length name), and this patch also
53        makes it give the same error for \k'' (previously it complained that that
54        was a reference to a non-existent subpattern).
56    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
57        this is right because (?- can be followed by option settings as well as by
58        digits. I have, however, made the messages clearer.
60    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
61        than the number used in the conditional) now cause a compile-time error.
62        This is actually not compatible with Perl, which accepts such patterns, but
63        treats the conditional as always being FALSE (as PCRE used to), but it
64        seems to me that giving a diagnostic is better.
66    8.  Change "alphameric" to the more common word "alphanumeric" in comments
67        and messages.
69    9.  Fix two occurrences of "backslash" in comments that should have been
70        "backspace".
72    10. Remove two redundant lines of code that can never be obeyed (their function
73        was moved elsewhere).
75    11. The program that makes PCRE's Unicode character property table had a bug
76        which caused it to generate incorrect table entries for sequences of
77        characters that have the same character type, but are in different scripts.
78        It amalgamated them into a single range, with the script of the first of
79        them. In other words, some characters were in the wrong script. There were
80        thirteen such cases, affecting characters in the following ranges:
82          U+002b0 - U+002c1
83          U+0060c - U+0060d
84          U+0061e - U+00612
85          U+0064b - U+0065e
86          U+0074d - U+0076d
87          U+01800 - U+01805
88          U+01d00 - U+01d77
89          U+01d9b - U+01dbf
90          U+0200b - U+0200f
91          U+030fc - U+030fe
92          U+03260 - U+0327f
93          U+0fb46 - U+0fbb1
94          U+10450 - U+1049d
96    12. The -o option (show only the matching part of a line) for pcregrep was not
97        compatible with GNU grep in that, if there was more than one match in a
98        line, it showed only the first of them. It now behaves in the same way as
99        GNU grep.
101    13. If the -o and -v options were combined for pcregrep, it printed a blank
102        line for every non-matching line. GNU grep prints nothing, and pcregrep now
103        does the same. The return code can be used to tell if there were any
104        non-matching lines.
106    14. Added --file-offsets and --line-offsets to pcregrep.
108    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
109        infinitely looping recursion. The bug was that positive lookaheads were not
110        being skipped when checking for a possible empty match (negative lookaheads
111        and both kinds of lookbehind were skipped).
113    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
114        inclusion of <windows.h> to before rather than after the definition of
115        INVALID_FILE_ATTRIBUTES (patch from David Byron).
117    17. Specifying a possessive quantifier with a specific limit for a Unicode
118        character property caused pcre_compile() to compile bad code, which led at
119        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
120        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
121        caused the error; without that there was no problem.
123    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
125    19. Added --enable-pcretest-libreadline.
127    20. In pcrecpp.cc, the variable 'count' was incremented twice in
128        RE::GlobalReplace(). As a result, the number of replacements returned was
129        double what it should be. I removed one of the increments, but Craig sent a
130        later patch that removed the other one (the right fix) and added unit tests
131        that check the return values (which was not done before).
133    21. Several CMake things:
135        (1) Arranged that, when cmake is used on Unix, the libraries end up with
136            the names libpcre and libpcreposix, not just pcre and pcreposix.
138        (2) The above change means that pcretest and pcregrep are now correctly
139            linked with the newly-built libraries, not previously installed ones.
143    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
144        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
145        UTF-8 newline character). The key issue is that the pattern starts .*;
146        this means that the match must be either at the beginning, or after a
147        newline. The bug was in the code for advancing after a failed match and
148        checking that the new position followed a newline. It was not taking
149        account of UTF-8 characters correctly.
151    23. PCRE was behaving differently from Perl in the way it recognized POSIX
152        character classes. PCRE was not treating the sequence [:...:] as a
153        character class unless the ... were all letters. Perl, however, seems to
154        allow any characters between [: and :], though of course it rejects as
155        unknown any "names" that contain non-letters, because all the known class
156        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
157        for example, whereas PCRE did not - it did not recognize a POSIX character
158        class. This seemed a bit dangerous, so the code has been changed to be
159        closer to Perl. The behaviour is not identical to Perl, because PCRE will
160        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
161        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
162        Perl does, and where it didn't before.
164    24. Rewrite so as to remove the single use of %n from pcregrep because in some
165        Windows environments %n is disabled by default.
168    Version 7.4 21-Sep-07
169    ---------------------
171    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
172        means that a class such as [\s] counted as "explicit reference to CR or
173        LF". That isn't really right - the whole point of the change was to try to
174        help when there was an actual mention of one of the two characters. So now
175        the change happens only if \r or \n (or a literal CR or LF) character is
176        encountered.
178    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
179        of both had grown to the point where there were only 3 bits left.
180        Fortunately, there was spare space in the data structure, and so I have
181        moved the internal flags into a new 16-bit field to free up more option
182        bits.
184    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
185        but did not set the internal JCHANGED flag - either of these is enough to
186        control the way the "get" function works - but the PCRE_INFO_JCHANGED
187        facility is supposed to tell if (?J) was ever used, so now (?J) at the
188        start sets both bits.
190    4.  Added options (at build time, compile time, exec time) to change \R from
191        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
193    5.  doc/pcresyntax.html was missing from the distribution.
195    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
196        compatibility, even though it is no longer used.
198    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
199        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
200        windows.h file is present (where different names are used). [This was
201        reversed later after testing - see 16 below.]
203    8.  Changed all #include <config.h> to #include "config.h". There were also
204        some further <pcre.h> cases that I changed to "pcre.h".
206    9.  When pcregrep was used with the --colour option, it missed the line ending
207        sequence off the lines that it output.
209    10. It was pointed out to me that arrays of string pointers cause lots of
210        relocations when a shared library is dynamically loaded. A technique of
211        using a single long string with a table of offsets can drastically reduce
212        these. I have refactored PCRE in four places to do this. The result is
213        dramatic:
215          Originally:                          290
216          After changing UCP table:            187
217          After changing error message table:   43
218          After changing table of "verbs"       36
219          After changing table of Posix names   22
221        Thanks to the folks working on Gregex for glib for this insight.
223    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
224        unicode-properties was also set.
226    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
228    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
229        checked only for CRLF.
231    14. Added casts to pcretest.c to avoid compiler warnings.
233    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
235    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
236        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
237        entirely. This removes changes made in 7 above.
239    17. The CMake files have been updated, and there is now more information about
240        building with CMake in the NON-UNIX-USE document.
243    Version 7.3 28-Aug-07
244    ---------------------
246     1. In the rejigging of the build system that eventually resulted in 7.1, the
247        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
248        brackets there is not right, since it causes compilers to look for an
249        installed pcre.h, not the version that is in the source that is being
250        compiled (which of course may be different). I have changed it back to:
252          #include "pcre.h"
254        I have a vague recollection that the change was concerned with compiling in
255        different directories, but in the new build system, that is taken care of
256        by the VPATH setting the Makefile.
258     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
259        when the subject happened to end in the byte 0x85 (e.g. if the last
260        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
261        characters but of course it shouldn't be taken as a newline when it is part
262        of another character. The bug was that, for an unlimited repeat of . in
263        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
264        characters when looking for a newline.
266     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
268     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
269        in debug output.
271     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
272        long printing in the pcrecpp unittest when running under MinGW.
274     6. ESC_K was left out of the EBCDIC table.
276     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
277        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
278        limit also applies to "virtual nesting" when a pattern is recursive, and in
279        this case 1000 isn't so big. I have been able to remove this limit at the
280        expense of backing off one optimization in certain circumstances. Normally,
281        when pcre_exec() would call its internal match() function recursively and
282        immediately return the result unconditionally, it uses a "tail recursion"
283        feature to save stack. However, when a subpattern that can match an empty
284        string has an unlimited repetition quantifier, it no longer makes this
285        optimization. That gives it a stack frame in which to save the data for
286        checking that an empty string has been matched. Previously this was taken
287        from the 1000-entry workspace that had been reserved. So now there is no
288        explicit limit, but more stack is used.
290     8. Applied Daniel's patches to solve problems with the import/export magic
291        syntax that is required for Windows, and which was going wrong for the
292        pcreposix and pcrecpp parts of the library. These were overlooked when this
293        problem was solved for the main library.
295     9. There were some crude static tests to avoid integer overflow when computing
296        the size of patterns that contain repeated groups with explicit upper
297        limits. As the maximum quantifier is 65535, the maximum group length was
298        set at 30,000 so that the product of these two numbers did not overflow a
299        32-bit integer. However, it turns out that people want to use groups that
300        are longer than 30,000 bytes (though not repeat them that many times).
301        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
302        made it possible to implement the integer overflow checks in a much more
303        dynamic way, which I have now done. The artificial limitation on group
304        length has been removed - we now have only the limit on the total length of
305        the compiled pattern, which depends on the LINK_SIZE setting.
307    10. Fixed a bug in the documentation for get/copy named substring when
308        duplicate names are permitted. If none of the named substrings are set, the
309        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
310        empty string.
312    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
313        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
314        because the ] is interpreted as the first data character and the
315        terminating ] is not found. PCRE has been made compatible with Perl in this
316        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
317        cause memory overwriting.
319    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
320        string has been matched (to stop an infinite loop). It was not recognizing
321        a conditional subpattern that could match an empty string if that
322        subpattern was within another subpattern. For example, it looped when
323        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
324        condition was not nested. This bug has been fixed.
326    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
327        past the start of the subject in the presence of bytes with the top bit
328        set, for example "\x8aBCD".
330    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
331        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
333    14. Optimized (?!) to (*FAIL).
335    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
336        This restricts code points to be within the range 0 to 0x10FFFF, excluding
337        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
338        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
339        does: it's just the validity check that is more restrictive.
341    16. Inserted checks for integer overflows during escape sequence (backslash)
342        processing, and also fixed erroneous offset values for syntax errors during
343        backslash processing.
345    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
346        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
348    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
349        caused an overrun.
351    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
352        something other than just ASCII characters) inside a group that had an
353        unlimited repeat caused a loop at compile time (while checking to see
354        whether the group could match an empty string).
356    20. Debugging a pattern containing \p or \P could cause a crash. For example,
357        [\P{Any}] did so. (Error in the code for printing property names.)
359    21. An orphan \E inside a character class could cause a crash.
361    22. A repeated capturing bracket such as (A)? could cause a wild memory
362        reference during compilation.
364    23. There are several functions in pcre_compile() that scan along a compiled
365        expression for various reasons (e.g. to see if it's fixed length for look
366        behind). There were bugs in these functions when a repeated \p or \P was
367        present in the pattern. These operators have additional parameters compared
368        with \d, etc, and these were not being taken into account when moving along
369        the compiled data. Specifically:
371        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
372            length.
374        (b) An item such as \pL+ within a repeated group could cause crashes or
375            loops.
377        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
378            "reference to non-existent subpattern" error.
380        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
382    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
383        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
385    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
387    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
388        character were causing crashes (broken optimization).
390    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
391        \p or \P) caused a compile-time loop.
393    28. More problems have arisen in unanchored patterns when CRLF is a valid line
394        break. For example, the unstudied pattern [\r\n]A does not match the string
395        "\r\nA" because change 7.0/46 below moves the current point on by two
396        characters after failing to match at the start. However, the pattern \nA
397        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
398        the same is true. There doesn't seem any very clean way out of this, but
399        what I have chosen to do makes the common cases work: PCRE now takes note
400        of whether there can be an explicit match for \r or \n anywhere in the
401        pattern, and if so, 7.0/46 no longer applies. As part of this change,
402        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
403        pattern has explicit CR or LF references.
405    29. Added (*CR) etc for changing newline setting at start of pattern.
408    Version 7.2 19-Jun-07
409    ---------------------
411     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
412        which is apparently normally available under Windows.
414     2. Re-jig the pcregrep tests with different newline settings in an attempt
415        to make them independent of the local environment's newline setting.
417     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
419     4. Some of the "internals" tests were previously cut out when the link size
420        was not 2, because the output contained actual offsets. The recent new
421        "Z" feature of pcretest means that these can be cut out, making the tests
422        usable with all link sizes.
424     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
425        stack recursion. This gives a massive performance boost under BSD, but just
426        a small improvement under Linux. However, it saves one field in the frame
427        in all cases.
429     6. Added more features from the forthcoming Perl 5.10:
431        (a) (?-n) (where n is a string of digits) is a relative subroutine or
432            recursion call. It refers to the nth most recently opened parentheses.
434        (b) (?+n) is also a relative subroutine call; it refers to the nth next
435            to be opened parentheses.
437        (c) Conditions that refer to capturing parentheses can be specified
438            relatively, for example, (?(-2)... or (?(+3)...
440        (d) \K resets the start of the current match so that everything before
441            is not part of it.
443        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
445        (f) \g{name} is another synonym - part of Perl 5.10's unification of
446            reference syntax.
448        (g) (?| introduces a group in which the numbering of parentheses in each
449            alternative starts with the same number.
451        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
453     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
456     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
457        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
458        for detecting groups that can match an empty string.
460     9. A pattern with a very large number of alternatives (more than several
461        hundred) was running out of internal workspace during the pre-compile
462        phase, where pcre_compile() figures out how much memory will be needed. A
463        bit of new cunning has reduced the workspace needed for groups with
464        alternatives. The 1000-alternative test pattern now uses 12 bytes of
465        workspace instead of running out of the 4096 that are available.
467    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
469    11. Applied patch from Google to remove an optimization that didn't quite work.
470        The report of the bug said:
472          pcrecpp::RE("a*").FullMatch("aaa") matches, while
473          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
474          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
476    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
477        it matched the wrong number of bytes.
480    Version 7.1 24-Apr-07
481    ---------------------
483     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
484        that is more "standard", making use of automake and other Autotools. There
485        is some re-arrangement of the files and adjustment of comments consequent
486        on this.
488     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
489        for recursive directory scanning broke on some systems because the files
490        are not scanned in any specific order and on different systems the order
491        was different. A call to "sort" has been inserted into RunGrepTest for the
492        approprate test as a short-term fix. In the longer term there may be an
493        alternative.
495     3. I had an email from Eric Raymond about problems translating some of PCRE's
496        man pages to HTML (despite the fact that I distribute HTML pages, some
497        people do their own conversions for various reasons). The problems
498        concerned the use of low-level troff macros .br and .in. I have therefore
499        removed all such uses from the man pages (some were redundant, some could
500        be replaced by .nf/.fi pairs). The 132html script that I use to generate
501        HTML has been updated to handle .nf/.fi and to complain if it encounters
502        .br or .in.
504     4. Updated comments in configure.ac that get placed in config.h.in and also
505        arranged for config.h to be included in the distribution, with the name
506        config.h.generic, for the benefit of those who have to compile without
507        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
509     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
510        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
511        makevp.bat for the current PCRE, using the additional files
512        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
514     6. A Windows user reported a minor discrepancy with test 2, which turned out
515        to be caused by a trailing space on an input line that had got lost in his
516        copy. The trailing space was an accident, so I've just removed it.
518     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
519        that is needed.
521     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
522        as "const" (a) because they are and (b) because it helps the PHP
523        maintainers who have recently made a script to detect big data structures
524        in the php code that should be moved to the .rodata section. I remembered
525        to update Builducptable as well, so it won't revert if ucptable.h is ever
526        re-created.
528     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
529        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
530        order to be able to cut out the UTF-8 tables in the latter when UTF-8
531        support is not required. This saves 1.5-2K of code, which is important in
532        some applications.
534        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
535        so as not to refer to the tables, even though these functions will never be
536        called when UTF-8 support is disabled. Otherwise there are problems with a
537        shared library.
539    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
541        (a) It was defining its arguments as char * instead of void *.
543        (b) It was assuming that all moves were upwards in memory; this was true
544            a long time ago when I wrote it, but is no longer the case.
546        The emulated memove() is provided for those environments that have neither
547        memmove() nor bcopy(). I didn't think anyone used it these days, but that
548        is clearly not the case, as these two bugs were recently reported.
550    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
551        and Detrail to create the HTML documentation, the .txt form of the man
552        pages, and it removes trailing spaces from listed files. It also creates
553        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
554        case, it wraps all the #defines with #ifndefs. This script should be run
555        before "make dist".
557    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
558        with Unicode property support.
560        (a) For a maximizing quantifier, if the two different cases of the
561            character were of different lengths in their UTF-8 codings (there are
562            some cases like this - I found 11), and the matching function had to
563            back up over a mixture of the two cases, it incorrectly assumed they
564            were both the same length.
566        (b) When PCRE was configured to use the heap rather than the stack for
567            recursion during matching, it was not correctly preserving the data for
568            the other case of a UTF-8 character when checking ahead for a match
569            while processing a minimizing repeat. If the check also involved
570            matching a wide character, but failed, corruption could cause an
571            erroneous result when trying to check for a repeat of the original
572            character.
574    13. Some tidying changes to the testing mechanism:
576        (a) The RunTest script now detects the internal link size and whether there
577            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
578            values substituted by "configure". (The RunGrepTest script already did
579            this for UTF-8.) The configure.ac script no longer substitutes the
580            relevant variables.
582        (b) The debugging options /B and /D in pcretest show the compiled bytecode
583            with length and offset values. This means that the output is different
584            for different internal link sizes. Test 2 is skipped for link sizes
585            other than 2 because of this, bypassing the problem. Unfortunately,
586            there was also a test in test 3 (the locale tests) that used /B and
587            failed for link sizes other than 2. Rather than cut the whole test out,
588            I have added a new /Z option to pcretest that replaces the length and
589            offset values with spaces. This is now used to make test 3 independent
590            of link size. (Test 2 will be tidied up later.)
592    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
593        segmentation fault instead of returning the appropriate error message.
595    15. In multiline mode when the newline sequence was set to "any", the pattern
596        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
597        This doesn't seem right; it now treats the CRLF combination as the line
598        ending, and so does not match in that case. It's only a pattern such as ^$
599        that would hit this one: something like ^ABC$ would have failed after \r
600        and then tried again after \r\n.
602    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
603        in an attempt to make files that differ only in their line terminators
604        compare equal. This works on Linux.
606    17. Under certain error circumstances pcregrep might try to free random memory
607        as it exited. This is now fixed, thanks to valgrind.
609    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
610        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
611        was because its rules for how to advance for /g after matching an empty
612        string at the end of a line did not allow for this case. They now check for
613        it specially.
615    20. pcretest is supposed to handle patterns and data of any length, by
616        extending its buffers when necessary. It was getting this wrong when the
617        buffer for a data line had to be extended.
619    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
620        CRLF as a newline sequence.
622    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
623        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
624        I have nevertheless tidied it up.
626    23. Added some casts to kill warnings from HP-UX ia64 compiler.
628    24. Added a man page for pcre-config.
631    Version 7.0 19-Dec-06
632    ---------------------
634     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
635        moving to gcc 4.1.1.
637     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
638        sys/time.h, which is documented as needed for this function. It doesn't
639        seem to matter on Linux, but it showed up on some releases of OS X.
641     3. It seems that there are systems where bytes whose values are greater than
642        127 match isprint() in the "C" locale. The "C" locale should be the
643        default when a C program starts up. In most systems, only ASCII printing
644        characters match isprint(). This difference caused the output from pcretest
645        to vary, making some of the tests fail. I have changed pcretest so that:
647        (a) When it is outputting text in the compiled version of a pattern, bytes
648            other than 32-126 are always shown as hex escapes.
650        (b) When it is outputting text that is a matched part of a subject string,
651            it does the same, unless a different locale has been set for the match
652            (using the /L modifier). In this case, it uses isprint() to decide.
654     4. Fixed a major bug that caused incorrect computation of the amount of memory
655        required for a compiled pattern when options that changed within the
656        pattern affected the logic of the preliminary scan that determines the
657        length. The relevant options are -x, and -i in UTF-8 mode. The result was
658        that the computed length was too small. The symptoms of this bug were
659        either the PCRE error "internal error: code overflow" from pcre_compile(),
660        or a glibc crash with a message such as "pcretest: free(): invalid next
661        size (fast)". Examples of patterns that provoked this bug (shown in
662        pcretest format) are:
664          /(?-x: )/x
665          /(?x)(?-x: \s*#\s*)/
666          /((?i)[\x{c0}])/8
667          /(?i:[\x{c0}])/8
669        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
670        is now done differently.
672     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
673        wrapper classes; (b) implement a new function in the C++ scanner that is
674        more efficient than the old way of doing things because it avoids levels of
675        recursion in the regex matching; (c) add a paragraph to the documentation
676        for the FullMatch() function.
678     6. The escape sequence \n was being treated as whatever was defined as
679        "newline". Not only was this contrary to the documentation, which states
680        that \n is character 10 (hex 0A), but it also went horribly wrong when
681        "newline" was defined as CRLF. This has been fixed.
683     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
684        was being set to -1 for the "end of line" case (supposedly a value that no
685        character can have). Though this value is never used (the check for end of
686        line is "zero bytes in current character"), it caused compiler complaints.
687        I've changed it to 0xffffffff.
689     8. In pcre_version.c, the version string was being built by a sequence of
690        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
691        string (as it is for production releases) called a macro with an empty
692        argument. The C standard says the result of this is undefined. The gcc
693        compiler treats it as an empty string (which was what was wanted) but it is
694        reported that Visual C gives an error. The source has been hacked around to
695        avoid this problem.
697     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
698        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
699        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
700        of them did).
702    10. Originally, pcretest opened its input and output without "b"; then I was
703        told that "b" was needed in some environments, so it was added for release
704        5.0 to both the input and output. (It makes no difference on Unix-like
705        systems.) Later I was told that it is wrong for the input on Windows. I've
706        now abstracted the modes into two macros, to make it easier to fiddle with
707        them, and removed "b" from the input mode under Windows.
709    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
711    12. Added -help and --help to pcretest as an official way of being reminded
712        of the options.
714    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
715        and pcrecpp.cc because they annoy compilers at high warning levels.
717    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
719    15. Fixed an occurrence of == in configure.ac that should have been = (shell
720        scripts are not C programs :-) and which was not noticed because it works
721        on Linux.
723    16. pcretest is supposed to handle any length of pattern and data line (as one
724        line or as a continued sequence of lines) by extending its input buffer if
725        necessary. This feature was broken for very long pattern lines, leading to
726        a string of junk being passed to pcre_compile() if the pattern was longer
727        than about 50K.
729    17. I have done a major re-factoring of the way pcre_compile() computes the
730        amount of memory needed for a compiled pattern. Previously, there was code
731        that made a preliminary scan of the pattern in order to do this. That was
732        OK when PCRE was new, but as the facilities have expanded, it has become
733        harder and harder to keep it in step with the real compile phase, and there
734        have been a number of bugs (see for example, 4 above). I have now found a
735        cunning way of running the real compile function in a "fake" mode that
736        enables it to compute how much memory it would need, while actually only
737        ever using a few hundred bytes of working memory and without too many
738        tests of the mode. This should make future maintenance and development
739        easier. A side effect of this work is that the limit of 200 on the nesting
740        depth of parentheses has been removed (though this was never a serious
741        limitation, I suspect). However, there is a downside: pcre_compile() now
742        runs more slowly than before (30% or more, depending on the pattern). I
743        hope this isn't a big issue. There is no effect on runtime performance.
745    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
746        newline (only possible for the last line of a file) and it was a
747        pattern that set a locale (followed by /Lsomething), pcretest crashed.
749    19. Added additional timing features to pcretest. (1) The -tm option now times
750        matching only, not compiling. (2) Both -t and -tm can be followed, as a
751        separate command line item, by a number that specifies the number of
752        repeats to use when timing. The default is 50000; this gives better
753        precision, but takes uncomfortably long for very large patterns.
755    20. Extended pcre_study() to be more clever in cases where a branch of a
756        subpattern has no definite first character. For example, (a*|b*)[cd] would
757        previously give no result from pcre_study(). Now it recognizes that the
758        first character must be a, b, c, or d.
760    21. There was an incorrect error "recursive call could loop indefinitely" if
761        a subpattern (or the entire pattern) that was being tested for matching an
762        empty string contained only one non-empty item after a nested subpattern.
763        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
764        incorrectly, because the \d was being skipped in the check.
766    22. The pcretest program now has a new pattern option /B and a command line
767        option -b, which is equivalent to adding /B to every pattern. This causes
768        it to show the compiled bytecode, without the additional information that
769        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
770        is the same as /B/I).
772    23. A new optimization is now able automatically to treat some sequences such
773        as a*b as a*+b. More specifically, if something simple (such as a character
774        or a simple class like \d) has an unlimited quantifier, and is followed by
775        something that cannot possibly match the quantified thing, the quantifier
776        is automatically "possessified".
778    24. A recursive reference to a subpattern whose number was greater than 39
779        went wrong under certain circumstances in UTF-8 mode. This bug could also
780        have affected the operation of pcre_study().
782    25. Realized that a little bit of performance could be had by replacing
783        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
785    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
787    27. Possessive quantifiers such as a++ were previously implemented by turning
788        them into atomic groups such as ($>a+). Now they have their own opcodes,
789        which improves performance. This includes the automatically created ones
790        from 23 above.
792    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
793        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
794        the first matched character to be a colon. This applied both to named and
795        numbered groups.
797    29. The ucpinternal.h header file was missing its idempotency #ifdef.
799    30. I was sent a "project" file called libpcre.a.dev which I understand makes
800        building PCRE on Windows easier, so I have included it in the distribution.
802    31. There is now a check in pcretest against a ridiculously large number being
803        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
804        loop, the loop is abandoned.
806    32. Forward references to subpatterns in conditions such as (?(2)...) where
807        subpattern 2 is defined later cause pcre_compile() to search forwards in
808        the pattern for the relevant set of parentheses. This search went wrong
809        when there were unescaped parentheses in a character class, parentheses
810        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
812    33. "Subroutine" calls and backreferences were previously restricted to
813        referencing subpatterns earlier in the regex. This restriction has now
814        been removed.
816    34. Added a number of extra features that are going to be in Perl 5.10. On the
817        whole, these are just syntactic alternatives for features that PCRE had
818        previously implemented using the Python syntax or my own invention. The
819        other formats are all retained for compatibility.
821        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
822            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
823            also .NET compatible.
825        (b) A recursion or subroutine call to a named group can now be defined as
826            (?&name) as well as (?P>name).
828        (c) A backreference to a named group can now be defined as \k<name> or
829            \k'name' as well as (?P=name). The new forms, as well as being in Perl
830            5.10, are also .NET compatible.
832        (d) A conditional reference to a named group can now use the syntax
833            (?(<name>) or (?('name') as well as (?(name).
835        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
836            groups (named and numbered) that are never evaluated inline, but can be
837            called as "subroutines" from elsewhere. In effect, the DEFINE condition
838            is always false. There may be only one alternative in such a group.
840        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
841            as the simple (?(R). The condition is true only if the most recent
842            recursion is that of the given number or name. It does not search out
843            through the entire recursion stack.
845        (g) The escape \gN or \g{N} has been added, where N is a positive or
846            negative number, specifying an absolute or relative reference.
848    35. Tidied to get rid of some further signed/unsigned compiler warnings and
849        some "unreachable code" warnings.
851    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
852        things, this adds five new scripts.
854    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
855        There were also incompatibilities regarding the handling of \Q..\E inside
856        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
857        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
859    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
860        matches an empty string, and forcibly breaks the loop. There were bugs in
861        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
862        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
863        separate and independent bugs (that affected different cases) have been
864        fixed.
866    39. Refactored the code to abolish the use of different opcodes for small
867        capturing bracket numbers. This is a tidy that I avoided doing when I
868        removed the limit on the number of capturing brackets for 3.5 back in 2001.
869        The new approach is not only tidier, it makes it possible to reduce the
870        memory needed to fix the previous bug (38).
872    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
873        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
874        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
875        mode.
877    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
878        report.
880    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
881        copy construction and assignment in the C++ wrapper.
883    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
884        couple of bugs that could have given wrong results in the "--newline=crlf"
885        case.
887    44. Added a number of casts and did some reorganization of signed/unsigned int
888        variables following suggestions from Dair Grant. Also renamed the variable
889        "this" as "item" because it is a C++ keyword.
891    45. Arranged for dftables to add
893          #include "pcre_internal.h"
895        to pcre_chartables.c because without it, gcc 4.x may remove the array
896        definition from the final binary if PCRE is built into a static library and
897        dead code stripping is activated.
899    46. For an unanchored pattern, if a match attempt fails at the start of a
900        newline sequence, and the newline setting is CRLF or ANY, and the next two
901        characters are CRLF, advance by two characters instead of one.
904    Version 6.7 04-Jul-06
905    ---------------------
907     1. In order to handle tests when input lines are enormously long, pcretest has
908        been re-factored so that it automatically extends its buffers when
909        necessary. The code is crude, but this _is_ just a test program. The
910        default size has been increased from 32K to 50K.
912     2. The code in pcre_study() was using the value of the re argument before
913        testing it for NULL. (Of course, in any sensible call of the function, it
914        won't be NULL.)
916     3. The memmove() emulation function in pcre_internal.h, which is used on
917        systems that lack both memmove() and bcopy() - that is, hardly ever -
918        was missing a "static" storage class specifier.
920     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
921        containing an extended class (one that cannot be represented by a bitmap
922        because it contains high-valued characters or Unicode property items, e.g.
923        [\pZ]). Almost always one would set UTF-8 mode when processing such a
924        pattern, but PCRE should not loop if you do not (it no longer does).
925        [Detail: two cases were found: (a) a repeated subpattern containing an
926        extended class; (b) a recursive reference to a subpattern that followed a
927        previous extended class. It wasn't skipping over the extended class
928        correctly when UTF-8 mode was not set.]
930     5. A negated single-character class was not being recognized as fixed-length
931        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
932        compile error "lookbehind assertion is not fixed length".
934     6. The RunPerlTest auxiliary script was showing an unexpected difference
935        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
936        write a Perl script that can interpret lines of an input file either as
937        byte characters or as UTF-8, which is what "perltest" was being required to
938        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
939        can't do is switch easily at run time between having the "use utf8;" pragma
940        or not. In the end, I fudged it by using the RunPerlTest script to insert
941        "use utf8;" explicitly for the UTF-8 tests.
943     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
944        the end of the subject string, contrary to the documentation and to what
945        Perl does. This was true of both matching functions. Now it matches only at
946        the start of the subject and immediately after *internal* newlines.
948     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
949        a pointer to an int instead of a pointer to an unsigned long int. This
950        caused problems on 64-bit systems.
952     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
953        instance of the 'standard' template library not being so standard".
955    10. There was no check on the number of named subpatterns nor the maximum
956        length of a subpattern name. The product of these values is used to compute
957        the size of the memory block for a compiled pattern. By supplying a very
958        long subpattern name and a large number of named subpatterns, the size
959        computation could be caused to overflow. This is now prevented by limiting
960        the length of names to 32 characters, and the number of named subpatterns
961        to 10,000.
963    11. Subpatterns that are repeated with specific counts have to be replicated in
964        the compiled pattern. The size of memory for this was computed from the
965        length of the subpattern and the repeat count. The latter is limited to
966        65535, but there was no limit on the former, meaning that integer overflow
967        could in principle occur. The compiled length of a repeated subpattern is
968        now limited to 30,000 bytes in order to prevent this.
970    12. Added the optional facility to have named substrings with the same name.
972    13. Added the ability to use a named substring as a condition, using the
973        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
974        are numbers (not recommended). Forward references are permitted.
976    14. Added forward references in named backreferences (if you see what I mean).
978    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
979        pattern could run off the end of the subject. For example, the pattern
980        "(?s)(.{1,5})"8 did this with the subject "ab".
982    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
983        PCRE_CASELESS was set when matching characters that were quantified with ?
984        or *.
986    17. A character class other than a single negated character that had a minimum
987        but no maximum quantifier - for example [ab]{6,} - was not handled
988        correctly by pce_dfa_exec(). It would match only one character.
990    18. A valid (though odd) pattern that looked like a POSIX character
991        class but used an invalid character after [ (for example [[,abc,]]) caused
992        pcre_compile() to give the error "Failed: internal error: code overflow" or
993        in some cases to crash with a glibc free() error. This could even happen if
994        the pattern terminated after [[ but there just happened to be a sequence of
995        letters, a binary zero, and a closing ] in the memory that followed.
997    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
998        over the years. Originally (before any Unicode support), just the bottom 8
999        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1000        output from "man perlunicode" includes this:
1002          The regular expression compiler produces polymorphic opcodes.  That
1003          is, the pattern adapts to the data and automatically switches to
1004          the Unicode character scheme when presented with Unicode data--or
1005          instead uses a traditional byte scheme when presented with byte
1006          data.
1008        Sadly, a wide octal escape does not cause a switch, and in a string with
1009        no other multibyte characters, these octal escapes are treated as before.
1010        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1011        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1012        Unicode string.
1014        I have not perpetrated such confusion in PCRE. Up till now, it took just
1015        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1016        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1017        translate to the appropriate multibyte character.
1019    29. Applied some refactoring to reduce the number of warnings from Microsoft
1020        and Borland compilers. This has included removing the fudge introduced
1021        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1022        a warning about an unused variable.
1024    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1025        characters since release 4.0, because Perl (from release 5.004) does not.
1026        [Or at least, is documented not to: some releases seem to be in conflict
1027        with the documentation.] However, when a pattern was studied with
1028        pcre_study() and all its branches started with \s, PCRE still included VT
1029        as a possible starting character. Of course, this did no harm; it just
1030        caused an unnecessary match attempt.
1032    22. Removed a now-redundant internal flag bit that recorded the fact that case
1033        dependency changed within the pattern. This was once needed for "required
1034        byte" processing, but is no longer used. This recovers a now-scarce options
1035        bit. Also moved the least significant internal flag bit to the most-
1036        significant bit of the word, which was not previously used (hangover from
1037        the days when it was an int rather than a uint) to free up another bit for
1038        the future.
1040    23. Added support for CRLF line endings as well as CR and LF. As well as the
1041        default being selectable at build time, it can now be changed at runtime
1042        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1043        specify that it is scanning data with non-default line endings.
1045    24. Changed the definition of CXXLINK to make it agree with the definition of
1046        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1048    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1049        recursions. This makes a big different to stack usage for some patterns.
1051    26. If a subpattern containing a named recursion or subroutine reference such
1052        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1053        the space required for the compiled pattern went wrong and gave too small a
1054        value. Depending on the environment, this could lead to "Failed: internal
1055        error: code overflow at offset 49" or "glibc detected double free or
1056        corruption" errors.
1058    27. Applied patches from Google (a) to support the new newline modes and (b) to
1059        advance over multibyte UTF-8 characters in GlobalReplace.
1061    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1062        difference for some implementation of PCRE in some Windows version.
1064    29. Added some extra testing facilities to pcretest:
1066        \q<number>   in a data line sets the "match limit" value
1067        \Q<number>   in a data line sets the "match recursion limt" value
1068        -S <number>  sets the stack size, where <number> is in megabytes
1070        The -S option isn't available for Windows.
1073    Version 6.6 06-Feb-06
1074    ---------------------
1076     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1077        in pcreposix.h. I have copied the definition from pcre.h.
1079     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1080        because pcre.h is no longer a built file.
1082     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1083        not normally included in the compiled code.
1086    Version 6.5 01-Feb-06
1087    ---------------------
1089     1. When using the partial match feature with pcre_dfa_exec(), it was not
1090        anchoring the second and subsequent partial matches at the new starting
1091        point. This could lead to incorrect results. For example, with the pattern
1092        /1234/, partially matching against "123" and then "a4" gave a match.
1094     2. Changes to pcregrep:
1096        (a) All non-match returns from pcre_exec() were being treated as failures
1097            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1098            error message is output. Some extra information is given for the
1099            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1100            probably the only errors that are likely to be caused by users (by
1101            specifying a regex that has nested indefinite repeats, for instance).
1102            If there are more than 20 of these errors, pcregrep is abandoned.
1104        (b) A binary zero was treated as data while matching, but terminated the
1105            output line if it was written out. This has been fixed: binary zeroes
1106            are now no different to any other data bytes.
1108        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1109            used to set a locale for matching. The --locale=xxxx long option has
1110            been added (no short equivalent) to specify a locale explicitly on the
1111            pcregrep command, overriding the environment variables.
1113        (d) When -B was used with -n, some line numbers in the output were one less
1114            than they should have been.
1116        (e) Added the -o (--only-matching) option.
1118        (f) If -A or -C was used with -c (count only), some lines of context were
1119            accidentally printed for the final match.
1121        (g) Added the -H (--with-filename) option.
1123        (h) The combination of options -rh failed to suppress file names for files
1124            that were found from directory arguments.
1126        (i) Added the -D (--devices) and -d (--directories) options.
1128        (j) Added the -F (--fixed-strings) option.
1130        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1132        (l) Added the --colo(u)r option.
1134        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1135            is not present by default.
1137     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1138        items such as (?R) or (?1), when the recursion could match a number of
1139        alternatives. If it matched one of the alternatives, but subsequently,
1140        outside the recursion, there was a failure, the code tried to back up into
1141        the recursion. However, because of the way PCRE is implemented, this is not
1142        possible, and the result was an incorrect result from the match.
1144        In order to prevent this happening, the specification of recursion has
1145        been changed so that all such subpatterns are automatically treated as
1146        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1148     4. I had overlooked the fact that, in some locales, there are characters for
1149        which isalpha() is true but neither isupper() nor islower() are true. In
1150        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1151        and ordfeminine) are like this. This affected the treatment of \w and \W
1152        when they appeared in character classes, but not when they appeared outside
1153        a character class. The bit map for "word" characters is now created
1154        separately from the results of isalnum() instead of just taking it from the
1155        upper, lower, and digit maps. (Plus the underscore character, of course.)
1157     5. The above bug also affected the handling of POSIX character classes such as
1158        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1159        permanent tables. Instead, the bit maps for such a class were previously
1160        created as the appropriate unions of the upper, lower, and digit bitmaps.
1161        Now they are created by subtraction from the [[:word:]] class, which has
1162        its own bitmap.
1164     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1165        It is created by subtracting the vertical space characters (\x09, \x0a,
1166        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1167        subtraction was done in the overall bitmap for a character class, meaning
1168        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1169        be recognized. This bug has been fixed.
1171     7. Patches from the folks at Google:
1173          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1174          real life, but is still worth protecting against".
1176          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1177          regular expressions".
1179          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1180          have it.
1182          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1183          "configure" and the latter not, in order to fix a problem somebody had
1184          with compiling the Arg class on HP-UX.
1186          (e) Improve the error-handling of the C++ wrapper a little bit.
1188          (f) New tests for checking recursion limiting.
1190     8. The pcre_memmove() function, which is used only if the environment does not
1191        have a standard memmove() function (and is therefore rarely compiled),
1192        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1193        returning a result (though PCRE never actually uses the result).
1195     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1196        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1197        returned instead of calling malloc() with an overflowing number that would
1198        most likely cause subsequent chaos.
1200    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1202    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1203        with this option is matched, the nmatch and pmatch options of regexec() are
1204        ignored.
1206    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1207        provided in case anyone wants to the the POSIX interface with UTF-8
1208        strings.
1210    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1211        C++ linking (needed for some HP-UX environments).
1213    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1214        (unused parameter) and in the pcre_printint() function (omitted "default"
1215        switch label when the default is to do nothing).
1217    15. Added some code to make it possible, when PCRE is compiled as a C++
1218        library, to replace subject pointers for pcre_exec() with a smart pointer
1219        class, thus making it possible to process discontinuous strings.
1221    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1222        much the same function. They were added by different people who were trying
1223        to make PCRE easy to compile on non-Unix systems. It has been suggested
1224        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1225        for compiling on Windows systems. I have therefore replaced it with
1226        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1227        defaults to "extern" for C or "extern C" for C++, which works fine on
1228        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1229        SCOPE with something explicit in config.h. In addition:
1231        (a) pcreposix.h still had just "extern" instead of either of these macros;
1232            I have replaced it with PCRE_DATA_SCOPE.
1234        (b) Functions such as _pcre_xclass(), which are internal to the library,
1235            but external in the C sense, all had PCRE_EXPORT in their definitions.
1236            This is apparently wrong for the Windows case, so I have removed it.
1237            (It makes no difference on Unix-like systems.)
1239    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1240        of recursive calls to match(). This is different to MATCH_LIMIT because
1241        that limits the total number of calls to match(), not all of which increase
1242        the depth of recursion. Limiting the recursion depth limits the amount of
1243        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1244        when PCRE is compiled, and changed at run time. A patch from Google adds
1245        this functionality to the C++ interface.
1247    18. Changes to the handling of Unicode character properties:
1249        (a) Updated the table to Unicode 4.1.0.
1251        (b) Recognize characters that are not in the table as "Cn" (undefined).
1253        (c) I revised the way the table is implemented to a much improved format
1254            which includes recognition of ranges. It now supports the ranges that
1255            are defined in UnicodeData.txt, and it also amalgamates other
1256            characters into ranges. This has reduced the number of entries in the
1257            table from around 16,000 to around 3,000, thus reducing its size
1258            considerably. I realized I did not need to use a tree structure after
1259            all - a binary chop search is just as efficient. Having reduced the
1260            number of entries, I extended their size from 6 bytes to 8 bytes to
1261            allow for more data.
1263        (d) Added support for Unicode script names via properties such as \p{Han}.
1265    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1266        matching that character.
1268    20. When matching a repeated Unicode property with a minimum greater than zero,
1269        (for example \pL{2,}), PCRE could look past the end of the subject if it
1270        reached it while seeking the minimum number of characters. This could
1271        happen only if some of the characters were more than one byte long, because
1272        there is a check for at least the minimum number of bytes.
1274    21. Refactored the implementation of \p and \P so as to be more general, to
1275        allow for more different types of property in future. This has changed the
1276        compiled form incompatibly. Anybody with saved compiled patterns that use
1277        \p or \P will have to recompile them.
1279    22. Added "Any" and "L&" to the supported property types.
1281    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1282        but give a compile time error if the value is greater than 0xff.
1284    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1285        accidentally not being installed or uninstalled.
1287    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1288        made were to insert the current release number. This seemed silly, because
1289        it made things harder for people building PCRE on systems that don't run
1290        "configure". I have turned pcre.h into a distributed file, no longer built
1291        by "configure", with the version identification directly included. There is
1292        no longer a pcre.h.in file.
1294        However, this change necessitated a change to the pcre-config script as
1295        well. It is built from pcre-config.in, and one of the substitutions was the
1296        release number. I have updated configure.ac so that ./configure now finds
1297        the release number by grepping pcre.h.
1299    26. Added the ability to run the tests under valgrind.
1302    Version 6.4 05-Sep-05
1303    ---------------------
1305     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1306        "--" to be printed when multiple files were scanned, even when none of the
1307        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1308        consider it to be a bug, and have restored the previous behaviour.
1310     2. A couple of code tidies to get rid of compiler warnings.
1312     3. The pcretest program used to cheat by referring to symbols in the library
1313        whose names begin with _pcre_. These are internal symbols that are not
1314        really supposed to be visible externally, and in some environments it is
1315        possible to suppress them. The cheating is now confined to including
1316        certain files from the library's source, which is a bit cleaner.
1318     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1319        file's purpose clearer.
1321     5. Reorganized pcre_ucp_findchar().
1324    Version 6.3 15-Aug-05
1325    ---------------------
1327     1. The file libpcre.pc.in did not have general read permission in the tarball.
1329     2. There were some problems when building without C++ support:
1331        (a) If C++ support was not built, "make install" and "make test" still
1332            tried to test it.
1334        (b) There were problems when the value of CXX was explicitly set. Some
1335            changes have been made to try to fix these, and ...
1337        (c) --disable-cpp can now be used to explicitly disable C++ support.
1339        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1340            backslash in a target when C++ was disabled. This confuses some
1341            versions of "make", apparently. Using an intermediate variable solves
1342            this. (Same for CPP_LOBJ.)
1344     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1345        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1346        necessary on certain architectures.
1348     4. Added a setting of -export-symbols-regex to the link command to remove
1349        those symbols that are exported in the C sense, but actually are local
1350        within the library, and not documented. Their names all begin with
1351        "_pcre_". This is not a perfect job, because (a) we have to except some
1352        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1353        available (and never for static libraries). I have made a note to try to
1354        find a way round (a) in the future.
1357    Version 6.2 01-Aug-05
1358    ---------------------
1360     1. There was no test for integer overflow of quantifier values. A construction
1361        such as {1111111111111111} would give undefined results. What is worse, if
1362        a minimum quantifier for a parenthesized subpattern overflowed and became
1363        negative, the calculation of the memory size went wrong. This could have
1364        led to memory overwriting.
1366     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
1368     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
1369        operating environments where this matters.
1371     4. Applied Giuseppe Maxia's patch to add additional features for controlling
1372        PCRE options from within the C++ wrapper.
1374     5. Named capturing subpatterns were not being correctly counted when a pattern
1375        was compiled. This caused two problems: (a) If there were more than 100
1376        such subpatterns, the calculation of the memory needed for the whole
1377        compiled pattern went wrong, leading to an overflow error. (b) Numerical
1378        back references of the form \12, where the number was greater than 9, were
1379        not recognized as back references, even though there were sufficient
1380        previous subpatterns.
1382     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
1383        versions of gcc, e.g. 2.95.4.
1386    Version 6.1 21-Jun-05
1387    ---------------------
1389     1. There was one reference to the variable "posix" in pcretest.c that was not
1390        surrounded by "#if !defined NOPOSIX".
1392     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
1393        the cross-check on the old pcre_info() function, for the benefit of the
1394        cut-down version of PCRE that is currently imported into Exim.
1396     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
1397        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
1398        patterns that start (?i) but I don't think that matters. The use of (?i) is
1399        just an example; this all applies to the other options as well.
1401     4. Since libtool seems to echo the compile commands it is issuing, the output
1402        from "make" can be reduced a bit by putting "@" in front of each libtool
1403        compile command.
1405     5. Patch from the folks at Google for configure.in to be a bit more thorough
1406        in checking for a suitable C++ installation before trying to compile the
1407        C++ stuff. This should fix a reported problem when a compiler was present,
1408        but no suitable headers.
1410     6. The man pages all had just "PCRE" as their title. I have changed them to
1411        be the relevant file name. I have also arranged that these names are
1412        retained in the file doc/pcre.txt, which is a concatenation in text format
1413        of all the man pages except the little individual ones for each function.
1415     7. The NON-UNIX-USE file had not been updated for the different set of source
1416        files that come with release 6. I also added a few comments about the C++
1417        wrapper.
1420    Version 6.0 07-Jun-05
1421    ---------------------
1423     1. Some minor internal re-organization to help with my DFA experiments.
1425     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
1426        didn't matter for the library itself when fully configured, but did matter
1427        when compiling without UCP support, or within Exim, where the ucp files are
1428        not imported.
1430     3. Refactoring of the library code to split up the various functions into
1431        different source modules. The addition of the new DFA matching code (see
1432        below) to a single monolithic source would have made it really too
1433        unwieldy, quite apart from causing all the code to be include in a
1434        statically linked application, when only some functions are used. This is
1435        relevant even without the DFA addition now that patterns can be compiled in
1436        one application and matched in another.
1438        The downside of splitting up is that there have to be some external
1439        functions and data tables that are used internally in different modules of
1440        the library but which are not part of the API. These have all had their
1441        names changed to start with "_pcre_" so that they are unlikely to clash
1442        with other external names.
1444     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
1445        a different (DFA) algorithm. Although it is slower than the original
1446        function, it does have some advantages for certain types of matching
1447        problem.
1449     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
1450        including restarting after a partial match.
1452     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
1453        defined when compiling for Windows was sent to me. I have put it into the
1454        code, though I have no means of testing or verifying it.
1456     7. Added the pcre_refcount() auxiliary function.
1458     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
1459        match before or at the first newline in the subject string. In pcretest,
1460        the /f option on a pattern can be used to set this.
1462     9. A repeated \w when used in UTF-8 mode with characters greater than 256
1463        would behave wrongly. This has been present in PCRE since release 4.0.
1465    10. A number of changes to the pcregrep command:
1467        (a) Refactored how -x works; insert ^(...)$ instead of setting
1468            PCRE_ANCHORED and checking the length, in preparation for adding
1469            something similar for -w.
1471        (b) Added the -w (match as a word) option.
1473        (c) Refactored the way lines are read and buffered so as to have more
1474            than one at a time available.
1476        (d) Implemented a pcregrep test script.
1478        (e) Added the -M (multiline match) option. This allows patterns to match
1479            over several lines of the subject. The buffering ensures that at least
1480            8K, or the rest of the document (whichever is the shorter) is available
1481            for matching (and similarly the previous 8K for lookbehind assertions).
1483        (f) Changed the --help output so that it now says
1485              -w, --word-regex(p)
1487            instead of two lines, one with "regex" and the other with "regexp"
1488            because that confused at least one person since the short forms are the
1489            same. (This required a bit of code, as the output is generated
1490            automatically from a table. It wasn't just a text change.)
1492        (g) -- can be used to terminate pcregrep options if the next thing isn't an
1493            option but starts with a hyphen. Could be a pattern or a path name
1494            starting with a hyphen, for instance.
1496        (h) "-" can be given as a file name to represent stdin.
1498        (i) When file names are being printed, "(standard input)" is used for
1499            the standard input, for compatibility with GNU grep. Previously
1500            "<stdin>" was used.
1502        (j) The option --label=xxx can be used to supply a name to be used for
1503            stdin when file names are being printed. There is no short form.
1505        (k) Re-factored the options decoding logic because we are going to add
1506            two more options that take data. Such options can now be given in four
1507            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
1509        (l) Added the -A, -B, and -C options for requesting that lines of context
1510            around matches be printed.
1512        (m) Added the -L option to print the names of files that do not contain
1513            any matching lines, that is, the complement of -l.
1515        (n) The return code is 2 if any file cannot be opened, but pcregrep does
1516            continue to scan other files.
1518        (o) The -s option was incorrectly implemented. For compatibility with other
1519            greps, it now suppresses the error message for a non-existent or non-
1520            accessible file (but not the return code). There is a new option called
1521            -q that suppresses the output of matching lines, which was what -s was
1522            previously doing.
1524        (p) Added --include and --exclude options to specify files for inclusion
1525            and exclusion when recursing.
1527    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
1528        Hopefully, it now does.
1530    12. Missing cast in pcre_study().
1532    13. Added an "uninstall" target to the makefile.
1534    14. Replaced "extern" in the function prototypes in Makefile.in with
1535        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
1536        world, but is set differently for Windows.
1538    15. Added a second compiling function called pcre_compile2(). The only
1539        difference is that it has an extra argument, which is a pointer to an
1540        integer error code. When there is a compile-time failure, this is set
1541        non-zero, in addition to the error test pointer being set to point to an
1542        error message. The new argument may be NULL if no error number is required
1543        (but then you may as well call pcre_compile(), which is now just a
1544        wrapper). This facility is provided because some applications need a
1545        numeric error indication, but it has also enabled me to tidy up the way
1546        compile-time errors are handled in the POSIX wrapper.
1548    16. Added VPATH=.libs to the makefile; this should help when building with one
1549        prefix path and installing with another. (Or so I'm told by someone who
1550        knows more about this stuff than I do.)
1552    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
1553        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
1554        match everything, including newlines. This is not POSIX-compatible, but
1555        somebody wanted the feature. From pcretest it can be activated by using
1556        both the P and the s flags.
1558    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
1560    19. libpcre.pc was being incorrectly installed as executable.
1562    20. A couple of places in pcretest check for end-of-line by looking for '\n';
1563        it now also looks for '\r' so that it will work unmodified on Windows.
1565    21. Added Google's contributed C++ wrapper to the distribution.
1567    22. Added some untidy missing memory free() calls in pcretest, to keep
1568        Electric Fence happy when testing.
1572    Version 5.0 13-Sep-04
1573    ---------------------
1575     1. Internal change: literal characters are no longer packed up into items
1576        containing multiple characters in a single byte-string. Each character
1577        is now matched using a separate opcode. However, there may be more than one
1578        byte in the character in UTF-8 mode.
1580     2. The pcre_callout_block structure has two new fields: pattern_position and
1581        next_item_length. These contain the offset in the pattern to the next match
1582        item, and its length, respectively.
1584     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
1585        insertion of callouts before each pattern item. Added the /C option to
1586        pcretest to make use of this.
1588     4. On the advice of a Windows user, the lines
1590          #if defined(_WIN32) || defined(WIN32)
1591          _setmode( _fileno( stdout ), 0x8000 );
1592          #endif  /* defined(_WIN32) || defined(WIN32) */
1594        have been added to the source of pcretest. This apparently does useful
1595        magic in relation to line terminators.
1597     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
1598        for the benefit of those environments where the "b" makes a difference.
1600     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
1601        to know about it. I have put a hack into configure.in that adds in code
1602        to set GCC=yes if CC=icc. This seems to end up at a point in the
1603        generated configure script that is early enough to affect the setting of
1604        compiler options, which is what is needed, but I have no means of testing
1605        whether it really works. (The user who reported this had patched the
1606        generated configure script, which of course I cannot do.)
1608        LATER: After change 22 below (new libtool files), the configure script
1609        seems to know about icc (and also ecc). Therefore, I have commented out
1610        this hack in configure.in.
1612     7. Added support for pkg-config (2 patches were sent in).
1614     8. Negated POSIX character classes that used a combination of internal tables
1615        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
1616        [[:^ascii]]. Typically, they would match almost any characters. The other
1617        POSIX classes were not broken in this way.
1619     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
1620        to find the match, as PCRE was deluded into thinking that the match had to
1621        start at the start point or following a newline. The same bug applied to
1622        patterns with negative forward assertions or any backward assertions
1623        preceding ".*" at the start, unless the pattern required a fixed first
1624        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
1626    10. In UTF-8 mode, when moving forwards in the subject after a failed match
1627        starting at the last subject character, bytes beyond the end of the subject
1628        string were read.
1630    11. Renamed the variable "class" as "classbits" to make life easier for C++
1631        users. (Previously there was a macro definition, but it apparently wasn't
1632        enough.)
1634    12. Added the new field "tables" to the extra data so that tables can be passed
1635        in at exec time, or the internal tables can be re-selected. This allows
1636        a compiled regex to be saved and re-used at a later time by a different
1637        program that might have everything at different addresses.
1639    13. Modified the pcre-config script so that, when run on Solaris, it shows a
1640        -R library as well as a -L library.
1642    14. The debugging options of pcretest (-d on the command line or D on a
1643        pattern) showed incorrect output for anything following an extended class
1644        that contained multibyte characters and which was followed by a quantifier.
1646    15. Added optional support for general category Unicode character properties
1647        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
1648        support. It adds about 90K to the size of the library. The meanings of the
1649        inbuilt class escapes such as \d and \s have NOT been changed.
1651    16. Updated pcredemo.c to include calls to free() to release the memory for the
1652        compiled pattern.
1654    17. The generated file chartables.c was being created in the source directory
1655        instead of in the building directory. This caused the build to fail if the
1656        source directory was different from the building directory, and was
1657        read-only.
1659    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
1660        file. No doubt somebody will tell me if they don't make sense... Also added
1661        Dan Mooney's comments about building on OpenVMS.
1663    19. Added support for partial matching via the PCRE_PARTIAL option for
1664        pcre_exec() and the \P data escape in pcretest.
1666    20. Extended pcretest with 3 new pattern features:
1668        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
1669              write the compiled pattern to the file whose name is "rest-of-line".
1670              This is a straight binary dump of the data, with the saved pointer to
1671              the character tables forced to be NULL. The study data, if any, is
1672              written too. After writing, pcretest reads a new pattern.
1674        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
1675              compiled pattern from the given file. There must not be any
1676              occurrences of "<" in the file name (pretty unlikely); if there are,
1677              pcretest will instead treat the initial "<" as a pattern delimiter.
1678              After reading in the pattern, pcretest goes on to read data lines as
1679              usual.
1681        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
1682              and 16-bit fields in a compiled pattern, to simulate a pattern that
1683              was compiled on a host of opposite endianness.
1685    21. The pcre-exec() function can now cope with patterns that were compiled on
1686        hosts of opposite endianness, with this restriction:
1688          As for any compiled expression that is saved and used later, the tables
1689          pointer field cannot be preserved; the extra_data field in the arguments
1690          to pcre_exec() should be used to pass in a tables address if a value
1691          other than the default internal tables were used at compile time.
1693    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
1694        now diagnosed as an error. Previously, most of the time, a negative number
1695        would have been treated as zero, but if in addition "ovector" was passed as
1696        NULL, a crash could occur.
1698    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
1699        new versions from the libtool 1.5 distribution (the last one is a copy of
1700        a file called libtool.m4). This seems to have fixed the need to patch
1701        "configure" to support Darwin 1.3 (which I used to do). However, I still
1702        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
1703        workstation).
1705    24. Changed the PCRE licence to be the more standard "BSD" licence.
1708    Version 4.5 01-Dec-03
1709    ---------------------
1711     1. There has been some re-arrangement of the code for the match() function so
1712        that it can be compiled in a version that does not call itself recursively.
1713        Instead, it keeps those local variables that need separate instances for
1714        each "recursion" in a frame on the heap, and gets/frees frames whenever it
1715        needs to "recurse". Keeping track of where control must go is done by means
1716        of setjmp/longjmp. The whole thing is implemented by a set of macros that
1717        hide most of the details from the main code, and operates only if
1718        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
1719        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
1720        operating.
1722        To make it easier for callers to provide specially tailored get/free
1723        functions for this usage, two new functions, pcre_stack_malloc, and
1724        pcre_stack_free, are used. They are always called in strict stacking order,
1725        and the size of block requested is always the same.
1727        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
1728        PCRE has been compiled to use the stack or the heap for recursion. The
1729        -C option of pcretest uses this to show which version is compiled.
1731        A new data escape \S, is added to pcretest; it causes the amounts of store
1732        obtained and freed by both kinds of malloc/free at match time to be added
1733        to the output.
1735     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
1736        what's available on my current Linux desktop machine.
1738     3. When matching a UTF-8 string, the test for a valid string at the start has
1739        been extended. If start_offset is not zero, PCRE now checks that it points
1740        to a byte that is the start of a UTF-8 character. If not, it returns
1741        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
1742        this is necessary because there may be backward assertions in the pattern.
1743        When matching the same subject several times, it may save resources to use
1744        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
1746     4. The code for checking the validity of UTF-8 strings has been tightened so
1747        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
1748        containing "overlong sequences".
1750     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
1751        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
1752        should have been "&", but it just so happened that all the cases this let
1753        through by mistake were picked up later in the function.
1755     6. I had used a variable called "isblank" - this is a C99 function, causing
1756        some compilers to warn. To avoid this, I renamed it (as "blankclass").
1758     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
1759        prompting; (b) run "./pcretest /dev/null" at the start of the test script
1760        so the version is shown; (c) stop "make test" echoing "./RunTest".
1762     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
1764     9. The prototype for memmove() for systems that don't have it was using
1765        size_t, but the inclusion of the header that defines size_t was later. I've
1766        moved the #includes for the C headers earlier to avoid this.
1768    10. Added some adjustments to the code to make it easier to compiler on certain
1769        special systems:
1771          (a) Some "const" qualifiers were missing.
1772          (b) Added the macro EXPORT before all exported functions; by default this
1773              is defined to be empty.
1774          (c) Changed the dftables auxiliary program (that builds chartables.c) so
1775              that it reads its output file name as an argument instead of writing
1776              to the standard output and assuming this can be redirected.
1778    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
1779        class containing characters with values greater than 255, PCRE compilation
1780        went into a loop.
1782    12. A recursive reference to a subpattern that was within another subpattern
1783        that had a minimum quantifier of zero caused PCRE to crash. For example,
1784        (x(y(?2))z)? provoked this bug with a subject that got as far as the
1785        recursion. If the recursively-called subpattern itself had a zero repeat,
1786        that was OK.
1788    13. In pcretest, the buffer for reading a data line was set at 30K, but the
1789        buffer into which it was copied (for escape processing) was still set at
1790        1024, so long lines caused crashes.
1792    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
1793        "internal error: code overflow...". This applied to any character class
1794        that was followed by a possessive quantifier.
1796    15. Modified the Makefile to add libpcre.la as a prerequisite for
1797        libpcreposix.la because I was told this is needed for a parallel build to
1798        work.
1800    16. If a pattern that contained .* following optional items at the start was
1801        studied, the wrong optimizing data was generated, leading to matching
1802        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
1803        matching string must start with a or b or c. The correct conclusion for
1804        this pattern is that a match can start with any character.
1807    Version 4.4 13-Aug-03
1808    ---------------------
1810     1. In UTF-8 mode, a character class containing characters with values between
1811        127 and 255 was not handled correctly if the compiled pattern was studied.
1812        In fixing this, I have also improved the studying algorithm for such
1813        classes (slightly).
1815     2. Three internal functions had redundant arguments passed to them. Removal
1816        might give a very teeny performance improvement.
1818     3. Documentation bug: the value of the capture_top field in a callout is *one
1819        more than* the number of the hightest numbered captured substring.
1821     4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
1822        in incorrectly linking with a previously installed version. They now link
1823        explicitly with libpcre.la.
1825     5. configure.in no longer needs to recognize Cygwin specially.
1827     6. A problem in pcre.in for Windows platforms is fixed.
1829     7. If a pattern was successfully studied, and the -d (or /D) flag was given to
1830        pcretest, it used to include the size of the study block as part of its
1831        output. Unfortunately, the structure contains a field that has a different
1832        size on different hardware architectures. This meant that the tests that
1833        showed this size failed. As the block is currently always of a fixed size,
1834        this information isn't actually particularly useful in pcretest output, so
1835        I have just removed it.
1837     8. Three pre-processor statements accidentally did not start in column 1.
1838        Sadly, there are *still* compilers around that complain, even though
1839        standard C has not required this for well over a decade. Sigh.
1841     9. In pcretest, the code for checking callouts passed small integers in the
1842        callout_data field, which is a void * field. However, some picky compilers
1843        complained about the casts involved for this on 64-bit systems. Now
1844        pcretest passes the address of the small integer instead, which should get
1845        rid of the warnings.
1847    10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
1848        both compile and run time, and gives an error if an invalid UTF-8 sequence
1849        is found. There is a option for disabling this check in cases where the
1850        string is known to be correct and/or the maximum performance is wanted.
1852    11. In response to a bug report, I changed one line in Makefile.in from
1854            -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
1855        to
1856            -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
1858        to look similar to other lines, but I have no way of telling whether this
1859        is the right thing to do, as I do not use Windows. No doubt I'll get told
1860        if it's wrong...
1863  Version 4.3 21-May-03  Version 4.3 21-May-03
1864  ---------------------  ---------------------

Removed from v.69  
changed lines
  Added in v.307

  ViewVC Help
Powered by ViewVC 1.1.5