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 233 by ph10, Tue Sep 11 11:26:11 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.4 10-Sep-07
5    ---------------------
7    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
8        means that a class such as [\s] counted as "explicit reference to CR or
9        LF". That isn't really right - the whole point of the change was to try to
10        help when there was an actual mention of one of the two characters. So now
11        the change happens only if \r or \n (or a literal CR or LF) character is
12        encountered.
14    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
15        of both had grown to the point where there were only 3 bits left.
16        Fortunately, there was spare space in the data structure, and so I have
17        moved the internal flags into a new 16-bit field to free up more option
18        bits.
20    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
21        but did not set the internal JCHANGED flag - either of these is enough to
22        control the way the "get" function works - but the PCRE_INFO_JCHANGED
23        facility is supposed to tell if (?J) was ever used, so now (?J) at the
24        start sets both bits.
26    4.  Added options (at build time, compile time, exec time) to change \R from
27        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
29    5.  doc/pcresyntax.html was missing from the distribution.
31    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
32        compatibility, even though it is no longer used.
35    Version 7.3 28-Aug-07
36    ---------------------
38     1. In the rejigging of the build system that eventually resulted in 7.1, the
39        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
40        brackets there is not right, since it causes compilers to look for an
41        installed pcre.h, not the version that is in the source that is being
42        compiled (which of course may be different). I have changed it back to:
44          #include "pcre.h"
46        I have a vague recollection that the change was concerned with compiling in
47        different directories, but in the new build system, that is taken care of
48        by the VPATH setting the Makefile.
50     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
51        when the subject happened to end in the byte 0x85 (e.g. if the last
52        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
53        characters but of course it shouldn't be taken as a newline when it is part
54        of another character. The bug was that, for an unlimited repeat of . in
55        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
56        characters when looking for a newline.
58     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
60     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
61        in debug output.
63     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
64        long printing in the pcrecpp unittest when running under MinGW.
66     6. ESC_K was left out of the EBCDIC table.
68     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
69        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
70        limit also applies to "virtual nesting" when a pattern is recursive, and in
71        this case 1000 isn't so big. I have been able to remove this limit at the
72        expense of backing off one optimization in certain circumstances. Normally,
73        when pcre_exec() would call its internal match() function recursively and
74        immediately return the result unconditionally, it uses a "tail recursion"
75        feature to save stack. However, when a subpattern that can match an empty
76        string has an unlimited repetition quantifier, it no longer makes this
77        optimization. That gives it a stack frame in which to save the data for
78        checking that an empty string has been matched. Previously this was taken
79        from the 1000-entry workspace that had been reserved. So now there is no
80        explicit limit, but more stack is used.
82     8. Applied Daniel's patches to solve problems with the import/export magic
83        syntax that is required for Windows, and which was going wrong for the
84        pcreposix and pcrecpp parts of the library. These were overlooked when this
85        problem was solved for the main library.
87     9. There were some crude static tests to avoid integer overflow when computing
88        the size of patterns that contain repeated groups with explicit upper
89        limits. As the maximum quantifier is 65535, the maximum group length was
90        set at 30,000 so that the product of these two numbers did not overflow a
91        32-bit integer. However, it turns out that people want to use groups that
92        are longer than 30,000 bytes (though not repeat them that many times).
93        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
94        made it possible to implement the integer overflow checks in a much more
95        dynamic way, which I have now done. The artificial limitation on group
96        length has been removed - we now have only the limit on the total length of
97        the compiled pattern, which depends on the LINK_SIZE setting.
99    10. Fixed a bug in the documentation for get/copy named substring when
100        duplicate names are permitted. If none of the named substrings are set, the
101        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
102        empty string.
104    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
105        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
106        because the ] is interpreted as the first data character and the
107        terminating ] is not found. PCRE has been made compatible with Perl in this
108        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
109        cause memory overwriting.
111    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
112        string has been matched (to stop an infinite loop). It was not recognizing
113        a conditional subpattern that could match an empty string if that
114        subpattern was within another subpattern. For example, it looped when
115        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
116        condition was not nested. This bug has been fixed.
118    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
119        past the start of the subject in the presence of bytes with the top bit
120        set, for example "\x8aBCD".
122    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
123        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
125    14. Optimized (?!) to (*FAIL).
127    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
128        This restricts code points to be within the range 0 to 0x10FFFF, excluding
129        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
130        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
131        does: it's just the validity check that is more restrictive.
133    16. Inserted checks for integer overflows during escape sequence (backslash)
134        processing, and also fixed erroneous offset values for syntax errors during
135        backslash processing.
137    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
138        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
140    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
141        caused an overrun.
143    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
144        something other than just ASCII characters) inside a group that had an
145        unlimited repeat caused a loop at compile time (while checking to see
146        whether the group could match an empty string).
148    20. Debugging a pattern containing \p or \P could cause a crash. For example,
149        [\P{Any}] did so. (Error in the code for printing property names.)
151    21. An orphan \E inside a character class could cause a crash.
153    22. A repeated capturing bracket such as (A)? could cause a wild memory
154        reference during compilation.
156    23. There are several functions in pcre_compile() that scan along a compiled
157        expression for various reasons (e.g. to see if it's fixed length for look
158        behind). There were bugs in these functions when a repeated \p or \P was
159        present in the pattern. These operators have additional parameters compared
160        with \d, etc, and these were not being taken into account when moving along
161        the compiled data. Specifically:
163        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
164            length.
166        (b) An item such as \pL+ within a repeated group could cause crashes or
167            loops.
169        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
170            "reference to non-existent subpattern" error.
172        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
174    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
175        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
177    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
179    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
180        character were causing crashes (broken optimization).
182    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
183        \p or \P) caused a compile-time loop.
185    28. More problems have arisen in unanchored patterns when CRLF is a valid line
186        break. For example, the unstudied pattern [\r\n]A does not match the string
187        "\r\nA" because change 7.0/46 below moves the current point on by two
188        characters after failing to match at the start. However, the pattern \nA
189        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
190        the same is true. There doesn't seem any very clean way out of this, but
191        what I have chosen to do makes the common cases work: PCRE now takes note
192        of whether there can be an explicit match for \r or \n anywhere in the
193        pattern, and if so, 7.0/46 no longer applies. As part of this change,
194        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
195        pattern has explicit CR or LF references.
197    29. Added (*CR) etc for changing newline setting at start of pattern.
200    Version 7.2 19-Jun-07
201    ---------------------
203     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
204        which is apparently normally available under Windows.
206     2. Re-jig the pcregrep tests with different newline settings in an attempt
207        to make them independent of the local environment's newline setting.
209     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
211     4. Some of the "internals" tests were previously cut out when the link size
212        was not 2, because the output contained actual offsets. The recent new
213        "Z" feature of pcretest means that these can be cut out, making the tests
214        usable with all link sizes.
216     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
217        stack recursion. This gives a massive performance boost under BSD, but just
218        a small improvement under Linux. However, it saves one field in the frame
219        in all cases.
221     6. Added more features from the forthcoming Perl 5.10:
223        (a) (?-n) (where n is a string of digits) is a relative subroutine or
224            recursion call. It refers to the nth most recently opened parentheses.
226        (b) (?+n) is also a relative subroutine call; it refers to the nth next
227            to be opened parentheses.
229        (c) Conditions that refer to capturing parentheses can be specified
230            relatively, for example, (?(-2)... or (?(+3)...
232        (d) \K resets the start of the current match so that everything before
233            is not part of it.
235        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
237        (f) \g{name} is another synonym - part of Perl 5.10's unification of
238            reference syntax.
240        (g) (?| introduces a group in which the numbering of parentheses in each
241            alternative starts with the same number.
243        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
245     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
248     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
249        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
250        for detecting groups that can match an empty string.
252     9. A pattern with a very large number of alternatives (more than several
253        hundred) was running out of internal workspace during the pre-compile
254        phase, where pcre_compile() figures out how much memory will be needed. A
255        bit of new cunning has reduced the workspace needed for groups with
256        alternatives. The 1000-alternative test pattern now uses 12 bytes of
257        workspace instead of running out of the 4096 that are available.
259    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
261    11. Applied patch from Google to remove an optimization that didn't quite work.
262        The report of the bug said:
264          pcrecpp::RE("a*").FullMatch("aaa") matches, while
265          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
266          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
268    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
269        it matched the wrong number of bytes.
272    Version 7.1 24-Apr-07
273    ---------------------
275     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
276        that is more "standard", making use of automake and other Autotools. There
277        is some re-arrangement of the files and adjustment of comments consequent
278        on this.
280     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
281        for recursive directory scanning broke on some systems because the files
282        are not scanned in any specific order and on different systems the order
283        was different. A call to "sort" has been inserted into RunGrepTest for the
284        approprate test as a short-term fix. In the longer term there may be an
285        alternative.
287     3. I had an email from Eric Raymond about problems translating some of PCRE's
288        man pages to HTML (despite the fact that I distribute HTML pages, some
289        people do their own conversions for various reasons). The problems
290        concerned the use of low-level troff macros .br and .in. I have therefore
291        removed all such uses from the man pages (some were redundant, some could
292        be replaced by .nf/.fi pairs). The 132html script that I use to generate
293        HTML has been updated to handle .nf/.fi and to complain if it encounters
294        .br or .in.
296     4. Updated comments in configure.ac that get placed in config.h.in and also
297        arranged for config.h to be included in the distribution, with the name
298        config.h.generic, for the benefit of those who have to compile without
299        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
301     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
302        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
303        makevp.bat for the current PCRE, using the additional files
304        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
306     6. A Windows user reported a minor discrepancy with test 2, which turned out
307        to be caused by a trailing space on an input line that had got lost in his
308        copy. The trailing space was an accident, so I've just removed it.
310     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
311        that is needed.
313     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
314        as "const" (a) because they are and (b) because it helps the PHP
315        maintainers who have recently made a script to detect big data structures
316        in the php code that should be moved to the .rodata section. I remembered
317        to update Builducptable as well, so it won't revert if ucptable.h is ever
318        re-created.
320     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
321        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
322        order to be able to cut out the UTF-8 tables in the latter when UTF-8
323        support is not required. This saves 1.5-2K of code, which is important in
324        some applications.
326        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
327        so as not to refer to the tables, even though these functions will never be
328        called when UTF-8 support is disabled. Otherwise there are problems with a
329        shared library.
331    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
333        (a) It was defining its arguments as char * instead of void *.
335        (b) It was assuming that all moves were upwards in memory; this was true
336            a long time ago when I wrote it, but is no longer the case.
338        The emulated memove() is provided for those environments that have neither
339        memmove() nor bcopy(). I didn't think anyone used it these days, but that
340        is clearly not the case, as these two bugs were recently reported.
342    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
343        and Detrail to create the HTML documentation, the .txt form of the man
344        pages, and it removes trailing spaces from listed files. It also creates
345        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
346        case, it wraps all the #defines with #ifndefs. This script should be run
347        before "make dist".
349    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
350        with Unicode property support.
352        (a) For a maximizing quantifier, if the two different cases of the
353            character were of different lengths in their UTF-8 codings (there are
354            some cases like this - I found 11), and the matching function had to
355            back up over a mixture of the two cases, it incorrectly assumed they
356            were both the same length.
358        (b) When PCRE was configured to use the heap rather than the stack for
359            recursion during matching, it was not correctly preserving the data for
360            the other case of a UTF-8 character when checking ahead for a match
361            while processing a minimizing repeat. If the check also involved
362            matching a wide character, but failed, corruption could cause an
363            erroneous result when trying to check for a repeat of the original
364            character.
366    13. Some tidying changes to the testing mechanism:
368        (a) The RunTest script now detects the internal link size and whether there
369            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
370            values substituted by "configure". (The RunGrepTest script already did
371            this for UTF-8.) The configure.ac script no longer substitutes the
372            relevant variables.
374        (b) The debugging options /B and /D in pcretest show the compiled bytecode
375            with length and offset values. This means that the output is different
376            for different internal link sizes. Test 2 is skipped for link sizes
377            other than 2 because of this, bypassing the problem. Unfortunately,
378            there was also a test in test 3 (the locale tests) that used /B and
379            failed for link sizes other than 2. Rather than cut the whole test out,
380            I have added a new /Z option to pcretest that replaces the length and
381            offset values with spaces. This is now used to make test 3 independent
382            of link size. (Test 2 will be tidied up later.)
384    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
385        segmentation fault instead of returning the appropriate error message.
387    15. In multiline mode when the newline sequence was set to "any", the pattern
388        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
389        This doesn't seem right; it now treats the CRLF combination as the line
390        ending, and so does not match in that case. It's only a pattern such as ^$
391        that would hit this one: something like ^ABC$ would have failed after \r
392        and then tried again after \r\n.
394    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
395        in an attempt to make files that differ only in their line terminators
396        compare equal. This works on Linux.
398    17. Under certain error circumstances pcregrep might try to free random memory
399        as it exited. This is now fixed, thanks to valgrind.
401    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
402        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
403        was because its rules for how to advance for /g after matching an empty
404        string at the end of a line did not allow for this case. They now check for
405        it specially.
407    20. pcretest is supposed to handle patterns and data of any length, by
408        extending its buffers when necessary. It was getting this wrong when the
409        buffer for a data line had to be extended.
411    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
412        CRLF as a newline sequence.
414    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
415        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
416        I have nevertheless tidied it up.
418    23. Added some casts to kill warnings from HP-UX ia64 compiler.
420    24. Added a man page for pcre-config.
423    Version 7.0 19-Dec-06
424    ---------------------
426     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
427        moving to gcc 4.1.1.
429     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
430        sys/time.h, which is documented as needed for this function. It doesn't
431        seem to matter on Linux, but it showed up on some releases of OS X.
433     3. It seems that there are systems where bytes whose values are greater than
434        127 match isprint() in the "C" locale. The "C" locale should be the
435        default when a C program starts up. In most systems, only ASCII printing
436        characters match isprint(). This difference caused the output from pcretest
437        to vary, making some of the tests fail. I have changed pcretest so that:
439        (a) When it is outputting text in the compiled version of a pattern, bytes
440            other than 32-126 are always shown as hex escapes.
442        (b) When it is outputting text that is a matched part of a subject string,
443            it does the same, unless a different locale has been set for the match
444            (using the /L modifier). In this case, it uses isprint() to decide.
446     4. Fixed a major bug that caused incorrect computation of the amount of memory
447        required for a compiled pattern when options that changed within the
448        pattern affected the logic of the preliminary scan that determines the
449        length. The relevant options are -x, and -i in UTF-8 mode. The result was
450        that the computed length was too small. The symptoms of this bug were
451        either the PCRE error "internal error: code overflow" from pcre_compile(),
452        or a glibc crash with a message such as "pcretest: free(): invalid next
453        size (fast)". Examples of patterns that provoked this bug (shown in
454        pcretest format) are:
456          /(?-x: )/x
457          /(?x)(?-x: \s*#\s*)/
458          /((?i)[\x{c0}])/8
459          /(?i:[\x{c0}])/8
461        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
462        is now done differently.
464     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
465        wrapper classes; (b) implement a new function in the C++ scanner that is
466        more efficient than the old way of doing things because it avoids levels of
467        recursion in the regex matching; (c) add a paragraph to the documentation
468        for the FullMatch() function.
470     6. The escape sequence \n was being treated as whatever was defined as
471        "newline". Not only was this contrary to the documentation, which states
472        that \n is character 10 (hex 0A), but it also went horribly wrong when
473        "newline" was defined as CRLF. This has been fixed.
475     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
476        was being set to -1 for the "end of line" case (supposedly a value that no
477        character can have). Though this value is never used (the check for end of
478        line is "zero bytes in current character"), it caused compiler complaints.
479        I've changed it to 0xffffffff.
481     8. In pcre_version.c, the version string was being built by a sequence of
482        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
483        string (as it is for production releases) called a macro with an empty
484        argument. The C standard says the result of this is undefined. The gcc
485        compiler treats it as an empty string (which was what was wanted) but it is
486        reported that Visual C gives an error. The source has been hacked around to
487        avoid this problem.
489     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
490        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
491        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
492        of them did).
494    10. Originally, pcretest opened its input and output without "b"; then I was
495        told that "b" was needed in some environments, so it was added for release
496        5.0 to both the input and output. (It makes no difference on Unix-like
497        systems.) Later I was told that it is wrong for the input on Windows. I've
498        now abstracted the modes into two macros, to make it easier to fiddle with
499        them, and removed "b" from the input mode under Windows.
501    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
503    12. Added -help and --help to pcretest as an official way of being reminded
504        of the options.
506    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
507        and pcrecpp.cc because they annoy compilers at high warning levels.
509    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
511    15. Fixed an occurrence of == in configure.ac that should have been = (shell
512        scripts are not C programs :-) and which was not noticed because it works
513        on Linux.
515    16. pcretest is supposed to handle any length of pattern and data line (as one
516        line or as a continued sequence of lines) by extending its input buffer if
517        necessary. This feature was broken for very long pattern lines, leading to
518        a string of junk being passed to pcre_compile() if the pattern was longer
519        than about 50K.
521    17. I have done a major re-factoring of the way pcre_compile() computes the
522        amount of memory needed for a compiled pattern. Previously, there was code
523        that made a preliminary scan of the pattern in order to do this. That was
524        OK when PCRE was new, but as the facilities have expanded, it has become
525        harder and harder to keep it in step with the real compile phase, and there
526        have been a number of bugs (see for example, 4 above). I have now found a
527        cunning way of running the real compile function in a "fake" mode that
528        enables it to compute how much memory it would need, while actually only
529        ever using a few hundred bytes of working memory and without too many
530        tests of the mode. This should make future maintenance and development
531        easier. A side effect of this work is that the limit of 200 on the nesting
532        depth of parentheses has been removed (though this was never a serious
533        limitation, I suspect). However, there is a downside: pcre_compile() now
534        runs more slowly than before (30% or more, depending on the pattern). I
535        hope this isn't a big issue. There is no effect on runtime performance.
537    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
538        newline (only possible for the last line of a file) and it was a
539        pattern that set a locale (followed by /Lsomething), pcretest crashed.
541    19. Added additional timing features to pcretest. (1) The -tm option now times
542        matching only, not compiling. (2) Both -t and -tm can be followed, as a
543        separate command line item, by a number that specifies the number of
544        repeats to use when timing. The default is 50000; this gives better
545        precision, but takes uncomfortably long for very large patterns.
547    20. Extended pcre_study() to be more clever in cases where a branch of a
548        subpattern has no definite first character. For example, (a*|b*)[cd] would
549        previously give no result from pcre_study(). Now it recognizes that the
550        first character must be a, b, c, or d.
552    21. There was an incorrect error "recursive call could loop indefinitely" if
553        a subpattern (or the entire pattern) that was being tested for matching an
554        empty string contained only one non-empty item after a nested subpattern.
555        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
556        incorrectly, because the \d was being skipped in the check.
558    22. The pcretest program now has a new pattern option /B and a command line
559        option -b, which is equivalent to adding /B to every pattern. This causes
560        it to show the compiled bytecode, without the additional information that
561        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
562        is the same as /B/I).
564    23. A new optimization is now able automatically to treat some sequences such
565        as a*b as a*+b. More specifically, if something simple (such as a character
566        or a simple class like \d) has an unlimited quantifier, and is followed by
567        something that cannot possibly match the quantified thing, the quantifier
568        is automatically "possessified".
570    24. A recursive reference to a subpattern whose number was greater than 39
571        went wrong under certain circumstances in UTF-8 mode. This bug could also
572        have affected the operation of pcre_study().
574    25. Realized that a little bit of performance could be had by replacing
575        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
577    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
579    27. Possessive quantifiers such as a++ were previously implemented by turning
580        them into atomic groups such as ($>a+). Now they have their own opcodes,
581        which improves performance. This includes the automatically created ones
582        from 23 above.
584    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
585        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
586        the first matched character to be a colon. This applied both to named and
587        numbered groups.
589    29. The ucpinternal.h header file was missing its idempotency #ifdef.
591    30. I was sent a "project" file called libpcre.a.dev which I understand makes
592        building PCRE on Windows easier, so I have included it in the distribution.
594    31. There is now a check in pcretest against a ridiculously large number being
595        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
596        loop, the loop is abandoned.
598    32. Forward references to subpatterns in conditions such as (?(2)...) where
599        subpattern 2 is defined later cause pcre_compile() to search forwards in
600        the pattern for the relevant set of parentheses. This search went wrong
601        when there were unescaped parentheses in a character class, parentheses
602        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
604    33. "Subroutine" calls and backreferences were previously restricted to
605        referencing subpatterns earlier in the regex. This restriction has now
606        been removed.
608    34. Added a number of extra features that are going to be in Perl 5.10. On the
609        whole, these are just syntactic alternatives for features that PCRE had
610        previously implemented using the Python syntax or my own invention. The
611        other formats are all retained for compatibility.
613        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
614            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
615            also .NET compatible.
617        (b) A recursion or subroutine call to a named group can now be defined as
618            (?&name) as well as (?P>name).
620        (c) A backreference to a named group can now be defined as \k<name> or
621            \k'name' as well as (?P=name). The new forms, as well as being in Perl
622            5.10, are also .NET compatible.
624        (d) A conditional reference to a named group can now use the syntax
625            (?(<name>) or (?('name') as well as (?(name).
627        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
628            groups (named and numbered) that are never evaluated inline, but can be
629            called as "subroutines" from elsewhere. In effect, the DEFINE condition
630            is always false. There may be only one alternative in such a group.
632        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
633            as the simple (?(R). The condition is true only if the most recent
634            recursion is that of the given number or name. It does not search out
635            through the entire recursion stack.
637        (g) The escape \gN or \g{N} has been added, where N is a positive or
638            negative number, specifying an absolute or relative reference.
640    35. Tidied to get rid of some further signed/unsigned compiler warnings and
641        some "unreachable code" warnings.
643    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
644        things, this adds five new scripts.
646    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
647        There were also incompatibilities regarding the handling of \Q..\E inside
648        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
649        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
651    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
652        matches an empty string, and forcibly breaks the loop. There were bugs in
653        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
654        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
655        separate and independent bugs (that affected different cases) have been
656        fixed.
658    39. Refactored the code to abolish the use of different opcodes for small
659        capturing bracket numbers. This is a tidy that I avoided doing when I
660        removed the limit on the number of capturing brackets for 3.5 back in 2001.
661        The new approach is not only tidier, it makes it possible to reduce the
662        memory needed to fix the previous bug (38).
664    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
665        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
666        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
667        mode.
669    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
670        report.
672    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
673        copy construction and assignment in the C++ wrapper.
675    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
676        couple of bugs that could have given wrong results in the "--newline=crlf"
677        case.
679    44. Added a number of casts and did some reorganization of signed/unsigned int
680        variables following suggestions from Dair Grant. Also renamed the variable
681        "this" as "item" because it is a C++ keyword.
683    45. Arranged for dftables to add
685          #include "pcre_internal.h"
687        to pcre_chartables.c because without it, gcc 4.x may remove the array
688        definition from the final binary if PCRE is built into a static library and
689        dead code stripping is activated.
691    46. For an unanchored pattern, if a match attempt fails at the start of a
692        newline sequence, and the newline setting is CRLF or ANY, and the next two
693        characters are CRLF, advance by two characters instead of one.
696    Version 6.7 04-Jul-06
697    ---------------------
699     1. In order to handle tests when input lines are enormously long, pcretest has
700        been re-factored so that it automatically extends its buffers when
701        necessary. The code is crude, but this _is_ just a test program. The
702        default size has been increased from 32K to 50K.
704     2. The code in pcre_study() was using the value of the re argument before
705        testing it for NULL. (Of course, in any sensible call of the function, it
706        won't be NULL.)
708     3. The memmove() emulation function in pcre_internal.h, which is used on
709        systems that lack both memmove() and bcopy() - that is, hardly ever -
710        was missing a "static" storage class specifier.
712     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
713        containing an extended class (one that cannot be represented by a bitmap
714        because it contains high-valued characters or Unicode property items, e.g.
715        [\pZ]). Almost always one would set UTF-8 mode when processing such a
716        pattern, but PCRE should not loop if you do not (it no longer does).
717        [Detail: two cases were found: (a) a repeated subpattern containing an
718        extended class; (b) a recursive reference to a subpattern that followed a
719        previous extended class. It wasn't skipping over the extended class
720        correctly when UTF-8 mode was not set.]
722     5. A negated single-character class was not being recognized as fixed-length
723        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
724        compile error "lookbehind assertion is not fixed length".
726     6. The RunPerlTest auxiliary script was showing an unexpected difference
727        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
728        write a Perl script that can interpret lines of an input file either as
729        byte characters or as UTF-8, which is what "perltest" was being required to
730        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
731        can't do is switch easily at run time between having the "use utf8;" pragma
732        or not. In the end, I fudged it by using the RunPerlTest script to insert
733        "use utf8;" explicitly for the UTF-8 tests.
735     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
736        the end of the subject string, contrary to the documentation and to what
737        Perl does. This was true of both matching functions. Now it matches only at
738        the start of the subject and immediately after *internal* newlines.
740     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
741        a pointer to an int instead of a pointer to an unsigned long int. This
742        caused problems on 64-bit systems.
744     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
745        instance of the 'standard' template library not being so standard".
747    10. There was no check on the number of named subpatterns nor the maximum
748        length of a subpattern name. The product of these values is used to compute
749        the size of the memory block for a compiled pattern. By supplying a very
750        long subpattern name and a large number of named subpatterns, the size
751        computation could be caused to overflow. This is now prevented by limiting
752        the length of names to 32 characters, and the number of named subpatterns
753        to 10,000.
755    11. Subpatterns that are repeated with specific counts have to be replicated in
756        the compiled pattern. The size of memory for this was computed from the
757        length of the subpattern and the repeat count. The latter is limited to
758        65535, but there was no limit on the former, meaning that integer overflow
759        could in principle occur. The compiled length of a repeated subpattern is
760        now limited to 30,000 bytes in order to prevent this.
762    12. Added the optional facility to have named substrings with the same name.
764    13. Added the ability to use a named substring as a condition, using the
765        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
766        are numbers (not recommended). Forward references are permitted.
768    14. Added forward references in named backreferences (if you see what I mean).
770    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
771        pattern could run off the end of the subject. For example, the pattern
772        "(?s)(.{1,5})"8 did this with the subject "ab".
774    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
775        PCRE_CASELESS was set when matching characters that were quantified with ?
776        or *.
778    17. A character class other than a single negated character that had a minimum
779        but no maximum quantifier - for example [ab]{6,} - was not handled
780        correctly by pce_dfa_exec(). It would match only one character.
782    18. A valid (though odd) pattern that looked like a POSIX character
783        class but used an invalid character after [ (for example [[,abc,]]) caused
784        pcre_compile() to give the error "Failed: internal error: code overflow" or
785        in some cases to crash with a glibc free() error. This could even happen if
786        the pattern terminated after [[ but there just happened to be a sequence of
787        letters, a binary zero, and a closing ] in the memory that followed.
789    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
790        over the years. Originally (before any Unicode support), just the bottom 8
791        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
792        output from "man perlunicode" includes this:
794          The regular expression compiler produces polymorphic opcodes.  That
795          is, the pattern adapts to the data and automatically switches to
796          the Unicode character scheme when presented with Unicode data--or
797          instead uses a traditional byte scheme when presented with byte
798          data.
800        Sadly, a wide octal escape does not cause a switch, and in a string with
801        no other multibyte characters, these octal escapes are treated as before.
802        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
803        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
804        Unicode string.
806        I have not perpetrated such confusion in PCRE. Up till now, it took just
807        the bottom 8 bits, as in old Perl. I have now made octal escapes with
808        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
809        translate to the appropriate multibyte character.
811    29. Applied some refactoring to reduce the number of warnings from Microsoft
812        and Borland compilers. This has included removing the fudge introduced
813        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
814        a warning about an unused variable.
816    21. PCRE has not included VT (character 0x0b) in the set of whitespace
817        characters since release 4.0, because Perl (from release 5.004) does not.
818        [Or at least, is documented not to: some releases seem to be in conflict
819        with the documentation.] However, when a pattern was studied with
820        pcre_study() and all its branches started with \s, PCRE still included VT
821        as a possible starting character. Of course, this did no harm; it just
822        caused an unnecessary match attempt.
824    22. Removed a now-redundant internal flag bit that recorded the fact that case
825        dependency changed within the pattern. This was once needed for "required
826        byte" processing, but is no longer used. This recovers a now-scarce options
827        bit. Also moved the least significant internal flag bit to the most-
828        significant bit of the word, which was not previously used (hangover from
829        the days when it was an int rather than a uint) to free up another bit for
830        the future.
832    23. Added support for CRLF line endings as well as CR and LF. As well as the
833        default being selectable at build time, it can now be changed at runtime
834        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
835        specify that it is scanning data with non-default line endings.
837    24. Changed the definition of CXXLINK to make it agree with the definition of
838        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
840    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
841        recursions. This makes a big different to stack usage for some patterns.
843    26. If a subpattern containing a named recursion or subroutine reference such
844        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
845        the space required for the compiled pattern went wrong and gave too small a
846        value. Depending on the environment, this could lead to "Failed: internal
847        error: code overflow at offset 49" or "glibc detected double free or
848        corruption" errors.
850    27. Applied patches from Google (a) to support the new newline modes and (b) to
851        advance over multibyte UTF-8 characters in GlobalReplace.
853    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
854        difference for some implementation of PCRE in some Windows version.
856    29. Added some extra testing facilities to pcretest:
858        \q<number>   in a data line sets the "match limit" value
859        \Q<number>   in a data line sets the "match recursion limt" value
860        -S <number>  sets the stack size, where <number> is in megabytes
862        The -S option isn't available for Windows.
865    Version 6.6 06-Feb-06
866    ---------------------
868     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
869        in pcreposix.h. I have copied the definition from pcre.h.
871     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
872        because pcre.h is no longer a built file.
874     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
875        not normally included in the compiled code.
878    Version 6.5 01-Feb-06
879    ---------------------
881     1. When using the partial match feature with pcre_dfa_exec(), it was not
882        anchoring the second and subsequent partial matches at the new starting
883        point. This could lead to incorrect results. For example, with the pattern
884        /1234/, partially matching against "123" and then "a4" gave a match.
886     2. Changes to pcregrep:
888        (a) All non-match returns from pcre_exec() were being treated as failures
889            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
890            error message is output. Some extra information is given for the
891            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
892            probably the only errors that are likely to be caused by users (by
893            specifying a regex that has nested indefinite repeats, for instance).
894            If there are more than 20 of these errors, pcregrep is abandoned.
896        (b) A binary zero was treated as data while matching, but terminated the
897            output line if it was written out. This has been fixed: binary zeroes
898            are now no different to any other data bytes.
900        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
901            used to set a locale for matching. The --locale=xxxx long option has
902            been added (no short equivalent) to specify a locale explicitly on the
903            pcregrep command, overriding the environment variables.
905        (d) When -B was used with -n, some line numbers in the output were one less
906            than they should have been.
908        (e) Added the -o (--only-matching) option.
910        (f) If -A or -C was used with -c (count only), some lines of context were
911            accidentally printed for the final match.
913        (g) Added the -H (--with-filename) option.
915        (h) The combination of options -rh failed to suppress file names for files
916            that were found from directory arguments.
918        (i) Added the -D (--devices) and -d (--directories) options.
920        (j) Added the -F (--fixed-strings) option.
922        (k) Allow "-" to be used as a file name for -f as well as for a data file.
924        (l) Added the --colo(u)r option.
926        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
927            is not present by default.
929     3. A nasty bug was discovered in the handling of recursive patterns, that is,
930        items such as (?R) or (?1), when the recursion could match a number of
931        alternatives. If it matched one of the alternatives, but subsequently,
932        outside the recursion, there was a failure, the code tried to back up into
933        the recursion. However, because of the way PCRE is implemented, this is not
934        possible, and the result was an incorrect result from the match.
936        In order to prevent this happening, the specification of recursion has
937        been changed so that all such subpatterns are automatically treated as
938        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
940     4. I had overlooked the fact that, in some locales, there are characters for
941        which isalpha() is true but neither isupper() nor islower() are true. In
942        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
943        and ordfeminine) are like this. This affected the treatment of \w and \W
944        when they appeared in character classes, but not when they appeared outside
945        a character class. The bit map for "word" characters is now created
946        separately from the results of isalnum() instead of just taking it from the
947        upper, lower, and digit maps. (Plus the underscore character, of course.)
949     5. The above bug also affected the handling of POSIX character classes such as
950        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
951        permanent tables. Instead, the bit maps for such a class were previously
952        created as the appropriate unions of the upper, lower, and digit bitmaps.
953        Now they are created by subtraction from the [[:word:]] class, which has
954        its own bitmap.
956     6. The [[:blank:]] character class matches horizontal, but not vertical space.
957        It is created by subtracting the vertical space characters (\x09, \x0a,
958        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
959        subtraction was done in the overall bitmap for a character class, meaning
960        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
961        be recognized. This bug has been fixed.
963     7. Patches from the folks at Google:
965          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
966          real life, but is still worth protecting against".
968          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
969          regular expressions".
971          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
972          have it.
974          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
975          "configure" and the latter not, in order to fix a problem somebody had
976          with compiling the Arg class on HP-UX.
978          (e) Improve the error-handling of the C++ wrapper a little bit.
980          (f) New tests for checking recursion limiting.
982     8. The pcre_memmove() function, which is used only if the environment does not
983        have a standard memmove() function (and is therefore rarely compiled),
984        contained two bugs: (a) use of int instead of size_t, and (b) it was not
985        returning a result (though PCRE never actually uses the result).
987     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
988        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
989        returned instead of calling malloc() with an overflowing number that would
990        most likely cause subsequent chaos.
992    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
994    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
995        with this option is matched, the nmatch and pmatch options of regexec() are
996        ignored.
998    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
999        provided in case anyone wants to the the POSIX interface with UTF-8
1000        strings.
1002    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1003        C++ linking (needed for some HP-UX environments).
1005    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1006        (unused parameter) and in the pcre_printint() function (omitted "default"
1007        switch label when the default is to do nothing).
1009    15. Added some code to make it possible, when PCRE is compiled as a C++
1010        library, to replace subject pointers for pcre_exec() with a smart pointer
1011        class, thus making it possible to process discontinuous strings.
1013    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1014        much the same function. They were added by different people who were trying
1015        to make PCRE easy to compile on non-Unix systems. It has been suggested
1016        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1017        for compiling on Windows systems. I have therefore replaced it with
1018        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1019        defaults to "extern" for C or "extern C" for C++, which works fine on
1020        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1021        SCOPE with something explicit in config.h. In addition:
1023        (a) pcreposix.h still had just "extern" instead of either of these macros;
1024            I have replaced it with PCRE_DATA_SCOPE.
1026        (b) Functions such as _pcre_xclass(), which are internal to the library,
1027            but external in the C sense, all had PCRE_EXPORT in their definitions.
1028            This is apparently wrong for the Windows case, so I have removed it.
1029            (It makes no difference on Unix-like systems.)
1031    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1032        of recursive calls to match(). This is different to MATCH_LIMIT because
1033        that limits the total number of calls to match(), not all of which increase
1034        the depth of recursion. Limiting the recursion depth limits the amount of
1035        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1036        when PCRE is compiled, and changed at run time. A patch from Google adds
1037        this functionality to the C++ interface.
1039    18. Changes to the handling of Unicode character properties:
1041        (a) Updated the table to Unicode 4.1.0.
1043        (b) Recognize characters that are not in the table as "Cn" (undefined).
1045        (c) I revised the way the table is implemented to a much improved format
1046            which includes recognition of ranges. It now supports the ranges that
1047            are defined in UnicodeData.txt, and it also amalgamates other
1048            characters into ranges. This has reduced the number of entries in the
1049            table from around 16,000 to around 3,000, thus reducing its size
1050            considerably. I realized I did not need to use a tree structure after
1051            all - a binary chop search is just as efficient. Having reduced the
1052            number of entries, I extended their size from 6 bytes to 8 bytes to
1053            allow for more data.
1055        (d) Added support for Unicode script names via properties such as \p{Han}.
1057    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1058        matching that character.
1060    20. When matching a repeated Unicode property with a minimum greater than zero,
1061        (for example \pL{2,}), PCRE could look past the end of the subject if it
1062        reached it while seeking the minimum number of characters. This could
1063        happen only if some of the characters were more than one byte long, because
1064        there is a check for at least the minimum number of bytes.
1066    21. Refactored the implementation of \p and \P so as to be more general, to
1067        allow for more different types of property in future. This has changed the
1068        compiled form incompatibly. Anybody with saved compiled patterns that use
1069        \p or \P will have to recompile them.
1071    22. Added "Any" and "L&" to the supported property types.
1073    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1074        but give a compile time error if the value is greater than 0xff.
1076    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1077        accidentally not being installed or uninstalled.
1079    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1080        made were to insert the current release number. This seemed silly, because
1081        it made things harder for people building PCRE on systems that don't run
1082        "configure". I have turned pcre.h into a distributed file, no longer built
1083        by "configure", with the version identification directly included. There is
1084        no longer a pcre.h.in file.
1086        However, this change necessitated a change to the pcre-config script as
1087        well. It is built from pcre-config.in, and one of the substitutions was the
1088        release number. I have updated configure.ac so that ./configure now finds
1089        the release number by grepping pcre.h.
1091    26. Added the ability to run the tests under valgrind.
1094    Version 6.4 05-Sep-05
1095    ---------------------
1097     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1098        "--" to be printed when multiple files were scanned, even when none of the
1099        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1100        consider it to be a bug, and have restored the previous behaviour.
1102     2. A couple of code tidies to get rid of compiler warnings.
1104     3. The pcretest program used to cheat by referring to symbols in the library
1105        whose names begin with _pcre_. These are internal symbols that are not
1106        really supposed to be visible externally, and in some environments it is
1107        possible to suppress them. The cheating is now confined to including
1108        certain files from the library's source, which is a bit cleaner.
1110     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1111        file's purpose clearer.
1113     5. Reorganized pcre_ucp_findchar().
1116  Version 6.3 15-Aug-05  Version 6.3 15-Aug-05
1117  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5