ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5