ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 75 by nigel, Sat Feb 24 21:40:37 2007 UTC revision 268 by ph10, Thu Nov 15 10:28:09 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 7.5 12-Nov-07
5    ---------------------
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing).
27    Version 7.4 21-Sep-07
28    ---------------------
30    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
31        means that a class such as [\s] counted as "explicit reference to CR or
32        LF". That isn't really right - the whole point of the change was to try to
33        help when there was an actual mention of one of the two characters. So now
34        the change happens only if \r or \n (or a literal CR or LF) character is
35        encountered.
37    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
38        of both had grown to the point where there were only 3 bits left.
39        Fortunately, there was spare space in the data structure, and so I have
40        moved the internal flags into a new 16-bit field to free up more option
41        bits.
43    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
44        but did not set the internal JCHANGED flag - either of these is enough to
45        control the way the "get" function works - but the PCRE_INFO_JCHANGED
46        facility is supposed to tell if (?J) was ever used, so now (?J) at the
47        start sets both bits.
49    4.  Added options (at build time, compile time, exec time) to change \R from
50        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
52    5.  doc/pcresyntax.html was missing from the distribution.
54    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
55        compatibility, even though it is no longer used.
57    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
58        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
59        windows.h file is present (where different names are used). [This was
60        reversed later after testing - see 16 below.]
62    8.  Changed all #include <config.h> to #include "config.h". There were also
63        some further <pcre.h> cases that I changed to "pcre.h".
65    9.  When pcregrep was used with the --colour option, it missed the line ending
66        sequence off the lines that it output.
68    10. It was pointed out to me that arrays of string pointers cause lots of
69        relocations when a shared library is dynamically loaded. A technique of
70        using a single long string with a table of offsets can drastically reduce
71        these. I have refactored PCRE in four places to do this. The result is
72        dramatic:
74          Originally:                          290
75          After changing UCP table:            187
76          After changing error message table:   43
77          After changing table of "verbs"       36
78          After changing table of Posix names   22
80        Thanks to the folks working on Gregex for glib for this insight.
82    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
83        unicode-properties was also set.
85    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
87    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
88        checked only for CRLF.
90    14. Added casts to pcretest.c to avoid compiler warnings.
92    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
94    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
95        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
96        entirely. This removes changes made in 7 above.
98    17. The CMake files have been updated, and there is now more information about
99        building with CMake in the NON-UNIX-USE document.
102    Version 7.3 28-Aug-07
103    ---------------------
105     1. In the rejigging of the build system that eventually resulted in 7.1, the
106        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
107        brackets there is not right, since it causes compilers to look for an
108        installed pcre.h, not the version that is in the source that is being
109        compiled (which of course may be different). I have changed it back to:
111          #include "pcre.h"
113        I have a vague recollection that the change was concerned with compiling in
114        different directories, but in the new build system, that is taken care of
115        by the VPATH setting the Makefile.
117     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
118        when the subject happened to end in the byte 0x85 (e.g. if the last
119        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
120        characters but of course it shouldn't be taken as a newline when it is part
121        of another character. The bug was that, for an unlimited repeat of . in
122        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
123        characters when looking for a newline.
125     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
127     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
128        in debug output.
130     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
131        long printing in the pcrecpp unittest when running under MinGW.
133     6. ESC_K was left out of the EBCDIC table.
135     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
136        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
137        limit also applies to "virtual nesting" when a pattern is recursive, and in
138        this case 1000 isn't so big. I have been able to remove this limit at the
139        expense of backing off one optimization in certain circumstances. Normally,
140        when pcre_exec() would call its internal match() function recursively and
141        immediately return the result unconditionally, it uses a "tail recursion"
142        feature to save stack. However, when a subpattern that can match an empty
143        string has an unlimited repetition quantifier, it no longer makes this
144        optimization. That gives it a stack frame in which to save the data for
145        checking that an empty string has been matched. Previously this was taken
146        from the 1000-entry workspace that had been reserved. So now there is no
147        explicit limit, but more stack is used.
149     8. Applied Daniel's patches to solve problems with the import/export magic
150        syntax that is required for Windows, and which was going wrong for the
151        pcreposix and pcrecpp parts of the library. These were overlooked when this
152        problem was solved for the main library.
154     9. There were some crude static tests to avoid integer overflow when computing
155        the size of patterns that contain repeated groups with explicit upper
156        limits. As the maximum quantifier is 65535, the maximum group length was
157        set at 30,000 so that the product of these two numbers did not overflow a
158        32-bit integer. However, it turns out that people want to use groups that
159        are longer than 30,000 bytes (though not repeat them that many times).
160        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
161        made it possible to implement the integer overflow checks in a much more
162        dynamic way, which I have now done. The artificial limitation on group
163        length has been removed - we now have only the limit on the total length of
164        the compiled pattern, which depends on the LINK_SIZE setting.
166    10. Fixed a bug in the documentation for get/copy named substring when
167        duplicate names are permitted. If none of the named substrings are set, the
168        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
169        empty string.
171    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
172        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
173        because the ] is interpreted as the first data character and the
174        terminating ] is not found. PCRE has been made compatible with Perl in this
175        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
176        cause memory overwriting.
178    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
179        string has been matched (to stop an infinite loop). It was not recognizing
180        a conditional subpattern that could match an empty string if that
181        subpattern was within another subpattern. For example, it looped when
182        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
183        condition was not nested. This bug has been fixed.
185    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
186        past the start of the subject in the presence of bytes with the top bit
187        set, for example "\x8aBCD".
189    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
190        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
192    14. Optimized (?!) to (*FAIL).
194    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
195        This restricts code points to be within the range 0 to 0x10FFFF, excluding
196        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
197        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
198        does: it's just the validity check that is more restrictive.
200    16. Inserted checks for integer overflows during escape sequence (backslash)
201        processing, and also fixed erroneous offset values for syntax errors during
202        backslash processing.
204    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
205        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
207    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
208        caused an overrun.
210    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
211        something other than just ASCII characters) inside a group that had an
212        unlimited repeat caused a loop at compile time (while checking to see
213        whether the group could match an empty string).
215    20. Debugging a pattern containing \p or \P could cause a crash. For example,
216        [\P{Any}] did so. (Error in the code for printing property names.)
218    21. An orphan \E inside a character class could cause a crash.
220    22. A repeated capturing bracket such as (A)? could cause a wild memory
221        reference during compilation.
223    23. There are several functions in pcre_compile() that scan along a compiled
224        expression for various reasons (e.g. to see if it's fixed length for look
225        behind). There were bugs in these functions when a repeated \p or \P was
226        present in the pattern. These operators have additional parameters compared
227        with \d, etc, and these were not being taken into account when moving along
228        the compiled data. Specifically:
230        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
231            length.
233        (b) An item such as \pL+ within a repeated group could cause crashes or
234            loops.
236        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
237            "reference to non-existent subpattern" error.
239        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
241    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
242        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
244    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
246    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
247        character were causing crashes (broken optimization).
249    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
250        \p or \P) caused a compile-time loop.
252    28. More problems have arisen in unanchored patterns when CRLF is a valid line
253        break. For example, the unstudied pattern [\r\n]A does not match the string
254        "\r\nA" because change 7.0/46 below moves the current point on by two
255        characters after failing to match at the start. However, the pattern \nA
256        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
257        the same is true. There doesn't seem any very clean way out of this, but
258        what I have chosen to do makes the common cases work: PCRE now takes note
259        of whether there can be an explicit match for \r or \n anywhere in the
260        pattern, and if so, 7.0/46 no longer applies. As part of this change,
261        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
262        pattern has explicit CR or LF references.
264    29. Added (*CR) etc for changing newline setting at start of pattern.
267    Version 7.2 19-Jun-07
268    ---------------------
270     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
271        which is apparently normally available under Windows.
273     2. Re-jig the pcregrep tests with different newline settings in an attempt
274        to make them independent of the local environment's newline setting.
276     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
278     4. Some of the "internals" tests were previously cut out when the link size
279        was not 2, because the output contained actual offsets. The recent new
280        "Z" feature of pcretest means that these can be cut out, making the tests
281        usable with all link sizes.
283     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
284        stack recursion. This gives a massive performance boost under BSD, but just
285        a small improvement under Linux. However, it saves one field in the frame
286        in all cases.
288     6. Added more features from the forthcoming Perl 5.10:
290        (a) (?-n) (where n is a string of digits) is a relative subroutine or
291            recursion call. It refers to the nth most recently opened parentheses.
293        (b) (?+n) is also a relative subroutine call; it refers to the nth next
294            to be opened parentheses.
296        (c) Conditions that refer to capturing parentheses can be specified
297            relatively, for example, (?(-2)... or (?(+3)...
299        (d) \K resets the start of the current match so that everything before
300            is not part of it.
302        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
304        (f) \g{name} is another synonym - part of Perl 5.10's unification of
305            reference syntax.
307        (g) (?| introduces a group in which the numbering of parentheses in each
308            alternative starts with the same number.
310        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
312     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
315     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
316        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
317        for detecting groups that can match an empty string.
319     9. A pattern with a very large number of alternatives (more than several
320        hundred) was running out of internal workspace during the pre-compile
321        phase, where pcre_compile() figures out how much memory will be needed. A
322        bit of new cunning has reduced the workspace needed for groups with
323        alternatives. The 1000-alternative test pattern now uses 12 bytes of
324        workspace instead of running out of the 4096 that are available.
326    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
328    11. Applied patch from Google to remove an optimization that didn't quite work.
329        The report of the bug said:
331          pcrecpp::RE("a*").FullMatch("aaa") matches, while
332          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
333          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
335    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
336        it matched the wrong number of bytes.
339    Version 7.1 24-Apr-07
340    ---------------------
342     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
343        that is more "standard", making use of automake and other Autotools. There
344        is some re-arrangement of the files and adjustment of comments consequent
345        on this.
347     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
348        for recursive directory scanning broke on some systems because the files
349        are not scanned in any specific order and on different systems the order
350        was different. A call to "sort" has been inserted into RunGrepTest for the
351        approprate test as a short-term fix. In the longer term there may be an
352        alternative.
354     3. I had an email from Eric Raymond about problems translating some of PCRE's
355        man pages to HTML (despite the fact that I distribute HTML pages, some
356        people do their own conversions for various reasons). The problems
357        concerned the use of low-level troff macros .br and .in. I have therefore
358        removed all such uses from the man pages (some were redundant, some could
359        be replaced by .nf/.fi pairs). The 132html script that I use to generate
360        HTML has been updated to handle .nf/.fi and to complain if it encounters
361        .br or .in.
363     4. Updated comments in configure.ac that get placed in config.h.in and also
364        arranged for config.h to be included in the distribution, with the name
365        config.h.generic, for the benefit of those who have to compile without
366        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
368     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
369        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
370        makevp.bat for the current PCRE, using the additional files
371        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
373     6. A Windows user reported a minor discrepancy with test 2, which turned out
374        to be caused by a trailing space on an input line that had got lost in his
375        copy. The trailing space was an accident, so I've just removed it.
377     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
378        that is needed.
380     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
381        as "const" (a) because they are and (b) because it helps the PHP
382        maintainers who have recently made a script to detect big data structures
383        in the php code that should be moved to the .rodata section. I remembered
384        to update Builducptable as well, so it won't revert if ucptable.h is ever
385        re-created.
387     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
388        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
389        order to be able to cut out the UTF-8 tables in the latter when UTF-8
390        support is not required. This saves 1.5-2K of code, which is important in
391        some applications.
393        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
394        so as not to refer to the tables, even though these functions will never be
395        called when UTF-8 support is disabled. Otherwise there are problems with a
396        shared library.
398    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
400        (a) It was defining its arguments as char * instead of void *.
402        (b) It was assuming that all moves were upwards in memory; this was true
403            a long time ago when I wrote it, but is no longer the case.
405        The emulated memove() is provided for those environments that have neither
406        memmove() nor bcopy(). I didn't think anyone used it these days, but that
407        is clearly not the case, as these two bugs were recently reported.
409    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
410        and Detrail to create the HTML documentation, the .txt form of the man
411        pages, and it removes trailing spaces from listed files. It also creates
412        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
413        case, it wraps all the #defines with #ifndefs. This script should be run
414        before "make dist".
416    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
417        with Unicode property support.
419        (a) For a maximizing quantifier, if the two different cases of the
420            character were of different lengths in their UTF-8 codings (there are
421            some cases like this - I found 11), and the matching function had to
422            back up over a mixture of the two cases, it incorrectly assumed they
423            were both the same length.
425        (b) When PCRE was configured to use the heap rather than the stack for
426            recursion during matching, it was not correctly preserving the data for
427            the other case of a UTF-8 character when checking ahead for a match
428            while processing a minimizing repeat. If the check also involved
429            matching a wide character, but failed, corruption could cause an
430            erroneous result when trying to check for a repeat of the original
431            character.
433    13. Some tidying changes to the testing mechanism:
435        (a) The RunTest script now detects the internal link size and whether there
436            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
437            values substituted by "configure". (The RunGrepTest script already did
438            this for UTF-8.) The configure.ac script no longer substitutes the
439            relevant variables.
441        (b) The debugging options /B and /D in pcretest show the compiled bytecode
442            with length and offset values. This means that the output is different
443            for different internal link sizes. Test 2 is skipped for link sizes
444            other than 2 because of this, bypassing the problem. Unfortunately,
445            there was also a test in test 3 (the locale tests) that used /B and
446            failed for link sizes other than 2. Rather than cut the whole test out,
447            I have added a new /Z option to pcretest that replaces the length and
448            offset values with spaces. This is now used to make test 3 independent
449            of link size. (Test 2 will be tidied up later.)
451    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
452        segmentation fault instead of returning the appropriate error message.
454    15. In multiline mode when the newline sequence was set to "any", the pattern
455        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
456        This doesn't seem right; it now treats the CRLF combination as the line
457        ending, and so does not match in that case. It's only a pattern such as ^$
458        that would hit this one: something like ^ABC$ would have failed after \r
459        and then tried again after \r\n.
461    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
462        in an attempt to make files that differ only in their line terminators
463        compare equal. This works on Linux.
465    17. Under certain error circumstances pcregrep might try to free random memory
466        as it exited. This is now fixed, thanks to valgrind.
468    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
469        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
470        was because its rules for how to advance for /g after matching an empty
471        string at the end of a line did not allow for this case. They now check for
472        it specially.
474    20. pcretest is supposed to handle patterns and data of any length, by
475        extending its buffers when necessary. It was getting this wrong when the
476        buffer for a data line had to be extended.
478    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
479        CRLF as a newline sequence.
481    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
482        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
483        I have nevertheless tidied it up.
485    23. Added some casts to kill warnings from HP-UX ia64 compiler.
487    24. Added a man page for pcre-config.
490    Version 7.0 19-Dec-06
491    ---------------------
493     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
494        moving to gcc 4.1.1.
496     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
497        sys/time.h, which is documented as needed for this function. It doesn't
498        seem to matter on Linux, but it showed up on some releases of OS X.
500     3. It seems that there are systems where bytes whose values are greater than
501        127 match isprint() in the "C" locale. The "C" locale should be the
502        default when a C program starts up. In most systems, only ASCII printing
503        characters match isprint(). This difference caused the output from pcretest
504        to vary, making some of the tests fail. I have changed pcretest so that:
506        (a) When it is outputting text in the compiled version of a pattern, bytes
507            other than 32-126 are always shown as hex escapes.
509        (b) When it is outputting text that is a matched part of a subject string,
510            it does the same, unless a different locale has been set for the match
511            (using the /L modifier). In this case, it uses isprint() to decide.
513     4. Fixed a major bug that caused incorrect computation of the amount of memory
514        required for a compiled pattern when options that changed within the
515        pattern affected the logic of the preliminary scan that determines the
516        length. The relevant options are -x, and -i in UTF-8 mode. The result was
517        that the computed length was too small. The symptoms of this bug were
518        either the PCRE error "internal error: code overflow" from pcre_compile(),
519        or a glibc crash with a message such as "pcretest: free(): invalid next
520        size (fast)". Examples of patterns that provoked this bug (shown in
521        pcretest format) are:
523          /(?-x: )/x
524          /(?x)(?-x: \s*#\s*)/
525          /((?i)[\x{c0}])/8
526          /(?i:[\x{c0}])/8
528        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
529        is now done differently.
531     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
532        wrapper classes; (b) implement a new function in the C++ scanner that is
533        more efficient than the old way of doing things because it avoids levels of
534        recursion in the regex matching; (c) add a paragraph to the documentation
535        for the FullMatch() function.
537     6. The escape sequence \n was being treated as whatever was defined as
538        "newline". Not only was this contrary to the documentation, which states
539        that \n is character 10 (hex 0A), but it also went horribly wrong when
540        "newline" was defined as CRLF. This has been fixed.
542     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
543        was being set to -1 for the "end of line" case (supposedly a value that no
544        character can have). Though this value is never used (the check for end of
545        line is "zero bytes in current character"), it caused compiler complaints.
546        I've changed it to 0xffffffff.
548     8. In pcre_version.c, the version string was being built by a sequence of
549        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
550        string (as it is for production releases) called a macro with an empty
551        argument. The C standard says the result of this is undefined. The gcc
552        compiler treats it as an empty string (which was what was wanted) but it is
553        reported that Visual C gives an error. The source has been hacked around to
554        avoid this problem.
556     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
557        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
558        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
559        of them did).
561    10. Originally, pcretest opened its input and output without "b"; then I was
562        told that "b" was needed in some environments, so it was added for release
563        5.0 to both the input and output. (It makes no difference on Unix-like
564        systems.) Later I was told that it is wrong for the input on Windows. I've
565        now abstracted the modes into two macros, to make it easier to fiddle with
566        them, and removed "b" from the input mode under Windows.
568    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
570    12. Added -help and --help to pcretest as an official way of being reminded
571        of the options.
573    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
574        and pcrecpp.cc because they annoy compilers at high warning levels.
576    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
578    15. Fixed an occurrence of == in configure.ac that should have been = (shell
579        scripts are not C programs :-) and which was not noticed because it works
580        on Linux.
582    16. pcretest is supposed to handle any length of pattern and data line (as one
583        line or as a continued sequence of lines) by extending its input buffer if
584        necessary. This feature was broken for very long pattern lines, leading to
585        a string of junk being passed to pcre_compile() if the pattern was longer
586        than about 50K.
588    17. I have done a major re-factoring of the way pcre_compile() computes the
589        amount of memory needed for a compiled pattern. Previously, there was code
590        that made a preliminary scan of the pattern in order to do this. That was
591        OK when PCRE was new, but as the facilities have expanded, it has become
592        harder and harder to keep it in step with the real compile phase, and there
593        have been a number of bugs (see for example, 4 above). I have now found a
594        cunning way of running the real compile function in a "fake" mode that
595        enables it to compute how much memory it would need, while actually only
596        ever using a few hundred bytes of working memory and without too many
597        tests of the mode. This should make future maintenance and development
598        easier. A side effect of this work is that the limit of 200 on the nesting
599        depth of parentheses has been removed (though this was never a serious
600        limitation, I suspect). However, there is a downside: pcre_compile() now
601        runs more slowly than before (30% or more, depending on the pattern). I
602        hope this isn't a big issue. There is no effect on runtime performance.
604    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
605        newline (only possible for the last line of a file) and it was a
606        pattern that set a locale (followed by /Lsomething), pcretest crashed.
608    19. Added additional timing features to pcretest. (1) The -tm option now times
609        matching only, not compiling. (2) Both -t and -tm can be followed, as a
610        separate command line item, by a number that specifies the number of
611        repeats to use when timing. The default is 50000; this gives better
612        precision, but takes uncomfortably long for very large patterns.
614    20. Extended pcre_study() to be more clever in cases where a branch of a
615        subpattern has no definite first character. For example, (a*|b*)[cd] would
616        previously give no result from pcre_study(). Now it recognizes that the
617        first character must be a, b, c, or d.
619    21. There was an incorrect error "recursive call could loop indefinitely" if
620        a subpattern (or the entire pattern) that was being tested for matching an
621        empty string contained only one non-empty item after a nested subpattern.
622        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
623        incorrectly, because the \d was being skipped in the check.
625    22. The pcretest program now has a new pattern option /B and a command line
626        option -b, which is equivalent to adding /B to every pattern. This causes
627        it to show the compiled bytecode, without the additional information that
628        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
629        is the same as /B/I).
631    23. A new optimization is now able automatically to treat some sequences such
632        as a*b as a*+b. More specifically, if something simple (such as a character
633        or a simple class like \d) has an unlimited quantifier, and is followed by
634        something that cannot possibly match the quantified thing, the quantifier
635        is automatically "possessified".
637    24. A recursive reference to a subpattern whose number was greater than 39
638        went wrong under certain circumstances in UTF-8 mode. This bug could also
639        have affected the operation of pcre_study().
641    25. Realized that a little bit of performance could be had by replacing
642        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
644    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
646    27. Possessive quantifiers such as a++ were previously implemented by turning
647        them into atomic groups such as ($>a+). Now they have their own opcodes,
648        which improves performance. This includes the automatically created ones
649        from 23 above.
651    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
652        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
653        the first matched character to be a colon. This applied both to named and
654        numbered groups.
656    29. The ucpinternal.h header file was missing its idempotency #ifdef.
658    30. I was sent a "project" file called libpcre.a.dev which I understand makes
659        building PCRE on Windows easier, so I have included it in the distribution.
661    31. There is now a check in pcretest against a ridiculously large number being
662        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
663        loop, the loop is abandoned.
665    32. Forward references to subpatterns in conditions such as (?(2)...) where
666        subpattern 2 is defined later cause pcre_compile() to search forwards in
667        the pattern for the relevant set of parentheses. This search went wrong
668        when there were unescaped parentheses in a character class, parentheses
669        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
671    33. "Subroutine" calls and backreferences were previously restricted to
672        referencing subpatterns earlier in the regex. This restriction has now
673        been removed.
675    34. Added a number of extra features that are going to be in Perl 5.10. On the
676        whole, these are just syntactic alternatives for features that PCRE had
677        previously implemented using the Python syntax or my own invention. The
678        other formats are all retained for compatibility.
680        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
681            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
682            also .NET compatible.
684        (b) A recursion or subroutine call to a named group can now be defined as
685            (?&name) as well as (?P>name).
687        (c) A backreference to a named group can now be defined as \k<name> or
688            \k'name' as well as (?P=name). The new forms, as well as being in Perl
689            5.10, are also .NET compatible.
691        (d) A conditional reference to a named group can now use the syntax
692            (?(<name>) or (?('name') as well as (?(name).
694        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
695            groups (named and numbered) that are never evaluated inline, but can be
696            called as "subroutines" from elsewhere. In effect, the DEFINE condition
697            is always false. There may be only one alternative in such a group.
699        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
700            as the simple (?(R). The condition is true only if the most recent
701            recursion is that of the given number or name. It does not search out
702            through the entire recursion stack.
704        (g) The escape \gN or \g{N} has been added, where N is a positive or
705            negative number, specifying an absolute or relative reference.
707    35. Tidied to get rid of some further signed/unsigned compiler warnings and
708        some "unreachable code" warnings.
710    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
711        things, this adds five new scripts.
713    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
714        There were also incompatibilities regarding the handling of \Q..\E inside
715        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
716        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
718    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
719        matches an empty string, and forcibly breaks the loop. There were bugs in
720        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
721        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
722        separate and independent bugs (that affected different cases) have been
723        fixed.
725    39. Refactored the code to abolish the use of different opcodes for small
726        capturing bracket numbers. This is a tidy that I avoided doing when I
727        removed the limit on the number of capturing brackets for 3.5 back in 2001.
728        The new approach is not only tidier, it makes it possible to reduce the
729        memory needed to fix the previous bug (38).
731    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
732        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
733        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
734        mode.
736    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
737        report.
739    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
740        copy construction and assignment in the C++ wrapper.
742    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
743        couple of bugs that could have given wrong results in the "--newline=crlf"
744        case.
746    44. Added a number of casts and did some reorganization of signed/unsigned int
747        variables following suggestions from Dair Grant. Also renamed the variable
748        "this" as "item" because it is a C++ keyword.
750    45. Arranged for dftables to add
752          #include "pcre_internal.h"
754        to pcre_chartables.c because without it, gcc 4.x may remove the array
755        definition from the final binary if PCRE is built into a static library and
756        dead code stripping is activated.
758    46. For an unanchored pattern, if a match attempt fails at the start of a
759        newline sequence, and the newline setting is CRLF or ANY, and the next two
760        characters are CRLF, advance by two characters instead of one.
763    Version 6.7 04-Jul-06
764    ---------------------
766     1. In order to handle tests when input lines are enormously long, pcretest has
767        been re-factored so that it automatically extends its buffers when
768        necessary. The code is crude, but this _is_ just a test program. The
769        default size has been increased from 32K to 50K.
771     2. The code in pcre_study() was using the value of the re argument before
772        testing it for NULL. (Of course, in any sensible call of the function, it
773        won't be NULL.)
775     3. The memmove() emulation function in pcre_internal.h, which is used on
776        systems that lack both memmove() and bcopy() - that is, hardly ever -
777        was missing a "static" storage class specifier.
779     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
780        containing an extended class (one that cannot be represented by a bitmap
781        because it contains high-valued characters or Unicode property items, e.g.
782        [\pZ]). Almost always one would set UTF-8 mode when processing such a
783        pattern, but PCRE should not loop if you do not (it no longer does).
784        [Detail: two cases were found: (a) a repeated subpattern containing an
785        extended class; (b) a recursive reference to a subpattern that followed a
786        previous extended class. It wasn't skipping over the extended class
787        correctly when UTF-8 mode was not set.]
789     5. A negated single-character class was not being recognized as fixed-length
790        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
791        compile error "lookbehind assertion is not fixed length".
793     6. The RunPerlTest auxiliary script was showing an unexpected difference
794        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
795        write a Perl script that can interpret lines of an input file either as
796        byte characters or as UTF-8, which is what "perltest" was being required to
797        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
798        can't do is switch easily at run time between having the "use utf8;" pragma
799        or not. In the end, I fudged it by using the RunPerlTest script to insert
800        "use utf8;" explicitly for the UTF-8 tests.
802     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
803        the end of the subject string, contrary to the documentation and to what
804        Perl does. This was true of both matching functions. Now it matches only at
805        the start of the subject and immediately after *internal* newlines.
807     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
808        a pointer to an int instead of a pointer to an unsigned long int. This
809        caused problems on 64-bit systems.
811     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
812        instance of the 'standard' template library not being so standard".
814    10. There was no check on the number of named subpatterns nor the maximum
815        length of a subpattern name. The product of these values is used to compute
816        the size of the memory block for a compiled pattern. By supplying a very
817        long subpattern name and a large number of named subpatterns, the size
818        computation could be caused to overflow. This is now prevented by limiting
819        the length of names to 32 characters, and the number of named subpatterns
820        to 10,000.
822    11. Subpatterns that are repeated with specific counts have to be replicated in
823        the compiled pattern. The size of memory for this was computed from the
824        length of the subpattern and the repeat count. The latter is limited to
825        65535, but there was no limit on the former, meaning that integer overflow
826        could in principle occur. The compiled length of a repeated subpattern is
827        now limited to 30,000 bytes in order to prevent this.
829    12. Added the optional facility to have named substrings with the same name.
831    13. Added the ability to use a named substring as a condition, using the
832        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
833        are numbers (not recommended). Forward references are permitted.
835    14. Added forward references in named backreferences (if you see what I mean).
837    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
838        pattern could run off the end of the subject. For example, the pattern
839        "(?s)(.{1,5})"8 did this with the subject "ab".
841    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
842        PCRE_CASELESS was set when matching characters that were quantified with ?
843        or *.
845    17. A character class other than a single negated character that had a minimum
846        but no maximum quantifier - for example [ab]{6,} - was not handled
847        correctly by pce_dfa_exec(). It would match only one character.
849    18. A valid (though odd) pattern that looked like a POSIX character
850        class but used an invalid character after [ (for example [[,abc,]]) caused
851        pcre_compile() to give the error "Failed: internal error: code overflow" or
852        in some cases to crash with a glibc free() error. This could even happen if
853        the pattern terminated after [[ but there just happened to be a sequence of
854        letters, a binary zero, and a closing ] in the memory that followed.
856    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
857        over the years. Originally (before any Unicode support), just the bottom 8
858        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
859        output from "man perlunicode" includes this:
861          The regular expression compiler produces polymorphic opcodes.  That
862          is, the pattern adapts to the data and automatically switches to
863          the Unicode character scheme when presented with Unicode data--or
864          instead uses a traditional byte scheme when presented with byte
865          data.
867        Sadly, a wide octal escape does not cause a switch, and in a string with
868        no other multibyte characters, these octal escapes are treated as before.
869        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
870        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
871        Unicode string.
873        I have not perpetrated such confusion in PCRE. Up till now, it took just
874        the bottom 8 bits, as in old Perl. I have now made octal escapes with
875        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
876        translate to the appropriate multibyte character.
878    29. Applied some refactoring to reduce the number of warnings from Microsoft
879        and Borland compilers. This has included removing the fudge introduced
880        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
881        a warning about an unused variable.
883    21. PCRE has not included VT (character 0x0b) in the set of whitespace
884        characters since release 4.0, because Perl (from release 5.004) does not.
885        [Or at least, is documented not to: some releases seem to be in conflict
886        with the documentation.] However, when a pattern was studied with
887        pcre_study() and all its branches started with \s, PCRE still included VT
888        as a possible starting character. Of course, this did no harm; it just
889        caused an unnecessary match attempt.
891    22. Removed a now-redundant internal flag bit that recorded the fact that case
892        dependency changed within the pattern. This was once needed for "required
893        byte" processing, but is no longer used. This recovers a now-scarce options
894        bit. Also moved the least significant internal flag bit to the most-
895        significant bit of the word, which was not previously used (hangover from
896        the days when it was an int rather than a uint) to free up another bit for
897        the future.
899    23. Added support for CRLF line endings as well as CR and LF. As well as the
900        default being selectable at build time, it can now be changed at runtime
901        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
902        specify that it is scanning data with non-default line endings.
904    24. Changed the definition of CXXLINK to make it agree with the definition of
905        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
907    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
908        recursions. This makes a big different to stack usage for some patterns.
910    26. If a subpattern containing a named recursion or subroutine reference such
911        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
912        the space required for the compiled pattern went wrong and gave too small a
913        value. Depending on the environment, this could lead to "Failed: internal
914        error: code overflow at offset 49" or "glibc detected double free or
915        corruption" errors.
917    27. Applied patches from Google (a) to support the new newline modes and (b) to
918        advance over multibyte UTF-8 characters in GlobalReplace.
920    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
921        difference for some implementation of PCRE in some Windows version.
923    29. Added some extra testing facilities to pcretest:
925        \q<number>   in a data line sets the "match limit" value
926        \Q<number>   in a data line sets the "match recursion limt" value
927        -S <number>  sets the stack size, where <number> is in megabytes
929        The -S option isn't available for Windows.
932    Version 6.6 06-Feb-06
933    ---------------------
935     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
936        in pcreposix.h. I have copied the definition from pcre.h.
938     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
939        because pcre.h is no longer a built file.
941     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
942        not normally included in the compiled code.
945    Version 6.5 01-Feb-06
946    ---------------------
948     1. When using the partial match feature with pcre_dfa_exec(), it was not
949        anchoring the second and subsequent partial matches at the new starting
950        point. This could lead to incorrect results. For example, with the pattern
951        /1234/, partially matching against "123" and then "a4" gave a match.
953     2. Changes to pcregrep:
955        (a) All non-match returns from pcre_exec() were being treated as failures
956            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
957            error message is output. Some extra information is given for the
958            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
959            probably the only errors that are likely to be caused by users (by
960            specifying a regex that has nested indefinite repeats, for instance).
961            If there are more than 20 of these errors, pcregrep is abandoned.
963        (b) A binary zero was treated as data while matching, but terminated the
964            output line if it was written out. This has been fixed: binary zeroes
965            are now no different to any other data bytes.
967        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
968            used to set a locale for matching. The --locale=xxxx long option has
969            been added (no short equivalent) to specify a locale explicitly on the
970            pcregrep command, overriding the environment variables.
972        (d) When -B was used with -n, some line numbers in the output were one less
973            than they should have been.
975        (e) Added the -o (--only-matching) option.
977        (f) If -A or -C was used with -c (count only), some lines of context were
978            accidentally printed for the final match.
980        (g) Added the -H (--with-filename) option.
982        (h) The combination of options -rh failed to suppress file names for files
983            that were found from directory arguments.
985        (i) Added the -D (--devices) and -d (--directories) options.
987        (j) Added the -F (--fixed-strings) option.
989        (k) Allow "-" to be used as a file name for -f as well as for a data file.
991        (l) Added the --colo(u)r option.
993        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
994            is not present by default.
996     3. A nasty bug was discovered in the handling of recursive patterns, that is,
997        items such as (?R) or (?1), when the recursion could match a number of
998        alternatives. If it matched one of the alternatives, but subsequently,
999        outside the recursion, there was a failure, the code tried to back up into
1000        the recursion. However, because of the way PCRE is implemented, this is not
1001        possible, and the result was an incorrect result from the match.
1003        In order to prevent this happening, the specification of recursion has
1004        been changed so that all such subpatterns are automatically treated as
1005        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1007     4. I had overlooked the fact that, in some locales, there are characters for
1008        which isalpha() is true but neither isupper() nor islower() are true. In
1009        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1010        and ordfeminine) are like this. This affected the treatment of \w and \W
1011        when they appeared in character classes, but not when they appeared outside
1012        a character class. The bit map for "word" characters is now created
1013        separately from the results of isalnum() instead of just taking it from the
1014        upper, lower, and digit maps. (Plus the underscore character, of course.)
1016     5. The above bug also affected the handling of POSIX character classes such as
1017        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1018        permanent tables. Instead, the bit maps for such a class were previously
1019        created as the appropriate unions of the upper, lower, and digit bitmaps.
1020        Now they are created by subtraction from the [[:word:]] class, which has
1021        its own bitmap.
1023     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1024        It is created by subtracting the vertical space characters (\x09, \x0a,
1025        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1026        subtraction was done in the overall bitmap for a character class, meaning
1027        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1028        be recognized. This bug has been fixed.
1030     7. Patches from the folks at Google:
1032          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1033          real life, but is still worth protecting against".
1035          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1036          regular expressions".
1038          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1039          have it.
1041          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1042          "configure" and the latter not, in order to fix a problem somebody had
1043          with compiling the Arg class on HP-UX.
1045          (e) Improve the error-handling of the C++ wrapper a little bit.
1047          (f) New tests for checking recursion limiting.
1049     8. The pcre_memmove() function, which is used only if the environment does not
1050        have a standard memmove() function (and is therefore rarely compiled),
1051        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1052        returning a result (though PCRE never actually uses the result).
1054     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1055        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1056        returned instead of calling malloc() with an overflowing number that would
1057        most likely cause subsequent chaos.
1059    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1061    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1062        with this option is matched, the nmatch and pmatch options of regexec() are
1063        ignored.
1065    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1066        provided in case anyone wants to the the POSIX interface with UTF-8
1067        strings.
1069    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1070        C++ linking (needed for some HP-UX environments).
1072    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1073        (unused parameter) and in the pcre_printint() function (omitted "default"
1074        switch label when the default is to do nothing).
1076    15. Added some code to make it possible, when PCRE is compiled as a C++
1077        library, to replace subject pointers for pcre_exec() with a smart pointer
1078        class, thus making it possible to process discontinuous strings.
1080    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1081        much the same function. They were added by different people who were trying
1082        to make PCRE easy to compile on non-Unix systems. It has been suggested
1083        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1084        for compiling on Windows systems. I have therefore replaced it with
1085        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1086        defaults to "extern" for C or "extern C" for C++, which works fine on
1087        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1088        SCOPE with something explicit in config.h. In addition:
1090        (a) pcreposix.h still had just "extern" instead of either of these macros;
1091            I have replaced it with PCRE_DATA_SCOPE.
1093        (b) Functions such as _pcre_xclass(), which are internal to the library,
1094            but external in the C sense, all had PCRE_EXPORT in their definitions.
1095            This is apparently wrong for the Windows case, so I have removed it.
1096            (It makes no difference on Unix-like systems.)
1098    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1099        of recursive calls to match(). This is different to MATCH_LIMIT because
1100        that limits the total number of calls to match(), not all of which increase
1101        the depth of recursion. Limiting the recursion depth limits the amount of
1102        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1103        when PCRE is compiled, and changed at run time. A patch from Google adds
1104        this functionality to the C++ interface.
1106    18. Changes to the handling of Unicode character properties:
1108        (a) Updated the table to Unicode 4.1.0.
1110        (b) Recognize characters that are not in the table as "Cn" (undefined).
1112        (c) I revised the way the table is implemented to a much improved format
1113            which includes recognition of ranges. It now supports the ranges that
1114            are defined in UnicodeData.txt, and it also amalgamates other
1115            characters into ranges. This has reduced the number of entries in the
1116            table from around 16,000 to around 3,000, thus reducing its size
1117            considerably. I realized I did not need to use a tree structure after
1118            all - a binary chop search is just as efficient. Having reduced the
1119            number of entries, I extended their size from 6 bytes to 8 bytes to
1120            allow for more data.
1122        (d) Added support for Unicode script names via properties such as \p{Han}.
1124    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1125        matching that character.
1127    20. When matching a repeated Unicode property with a minimum greater than zero,
1128        (for example \pL{2,}), PCRE could look past the end of the subject if it
1129        reached it while seeking the minimum number of characters. This could
1130        happen only if some of the characters were more than one byte long, because
1131        there is a check for at least the minimum number of bytes.
1133    21. Refactored the implementation of \p and \P so as to be more general, to
1134        allow for more different types of property in future. This has changed the
1135        compiled form incompatibly. Anybody with saved compiled patterns that use
1136        \p or \P will have to recompile them.
1138    22. Added "Any" and "L&" to the supported property types.
1140    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1141        but give a compile time error if the value is greater than 0xff.
1143    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1144        accidentally not being installed or uninstalled.
1146    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1147        made were to insert the current release number. This seemed silly, because
1148        it made things harder for people building PCRE on systems that don't run
1149        "configure". I have turned pcre.h into a distributed file, no longer built
1150        by "configure", with the version identification directly included. There is
1151        no longer a pcre.h.in file.
1153        However, this change necessitated a change to the pcre-config script as
1154        well. It is built from pcre-config.in, and one of the substitutions was the
1155        release number. I have updated configure.ac so that ./configure now finds
1156        the release number by grepping pcre.h.
1158    26. Added the ability to run the tests under valgrind.
1161    Version 6.4 05-Sep-05
1162    ---------------------
1164     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1165        "--" to be printed when multiple files were scanned, even when none of the
1166        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1167        consider it to be a bug, and have restored the previous behaviour.
1169     2. A couple of code tidies to get rid of compiler warnings.
1171     3. The pcretest program used to cheat by referring to symbols in the library
1172        whose names begin with _pcre_. These are internal symbols that are not
1173        really supposed to be visible externally, and in some environments it is
1174        possible to suppress them. The cheating is now confined to including
1175        certain files from the library's source, which is a bit cleaner.
1177     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1178        file's purpose clearer.
1180     5. Reorganized pcre_ucp_findchar().
1183    Version 6.3 15-Aug-05
1184    ---------------------
1186     1. The file libpcre.pc.in did not have general read permission in the tarball.
1188     2. There were some problems when building without C++ support:
1190        (a) If C++ support was not built, "make install" and "make test" still
1191            tried to test it.
1193        (b) There were problems when the value of CXX was explicitly set. Some
1194            changes have been made to try to fix these, and ...
1196        (c) --disable-cpp can now be used to explicitly disable C++ support.
1198        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
1199            backslash in a target when C++ was disabled. This confuses some
1200            versions of "make", apparently. Using an intermediate variable solves
1201            this. (Same for CPP_LOBJ.)
1203     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
1204        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
1205        necessary on certain architectures.
1207     4. Added a setting of -export-symbols-regex to the link command to remove
1208        those symbols that are exported in the C sense, but actually are local
1209        within the library, and not documented. Their names all begin with
1210        "_pcre_". This is not a perfect job, because (a) we have to except some
1211        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
1212        available (and never for static libraries). I have made a note to try to
1213        find a way round (a) in the future.
1216    Version 6.2 01-Aug-05
1217    ---------------------
1219     1. There was no test for integer overflow of quantifier values. A construction
1220        such as {1111111111111111} would give undefined results. What is worse, if
1221        a minimum quantifier for a parenthesized subpattern overflowed and became
1222        negative, the calculation of the memory size went wrong. This could have
1223        led to memory overwriting.
1225     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
1227     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
1228        operating environments where this matters.
1230     4. Applied Giuseppe Maxia's patch to add additional features for controlling
1231        PCRE options from within the C++ wrapper.
1233     5. Named capturing subpatterns were not being correctly counted when a pattern
1234        was compiled. This caused two problems: (a) If there were more than 100
1235        such subpatterns, the calculation of the memory needed for the whole
1236        compiled pattern went wrong, leading to an overflow error. (b) Numerical
1237        back references of the form \12, where the number was greater than 9, were
1238        not recognized as back references, even though there were sufficient
1239        previous subpatterns.
1241     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
1242        versions of gcc, e.g. 2.95.4.
1245    Version 6.1 21-Jun-05
1246    ---------------------
1248     1. There was one reference to the variable "posix" in pcretest.c that was not
1249        surrounded by "#if !defined NOPOSIX".
1251     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
1252        the cross-check on the old pcre_info() function, for the benefit of the
1253        cut-down version of PCRE that is currently imported into Exim.
1255     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
1256        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
1257        patterns that start (?i) but I don't think that matters. The use of (?i) is
1258        just an example; this all applies to the other options as well.
1260     4. Since libtool seems to echo the compile commands it is issuing, the output
1261        from "make" can be reduced a bit by putting "@" in front of each libtool
1262        compile command.
1264     5. Patch from the folks at Google for configure.in to be a bit more thorough
1265        in checking for a suitable C++ installation before trying to compile the
1266        C++ stuff. This should fix a reported problem when a compiler was present,
1267        but no suitable headers.
1269     6. The man pages all had just "PCRE" as their title. I have changed them to
1270        be the relevant file name. I have also arranged that these names are
1271        retained in the file doc/pcre.txt, which is a concatenation in text format
1272        of all the man pages except the little individual ones for each function.
1274     7. The NON-UNIX-USE file had not been updated for the different set of source
1275        files that come with release 6. I also added a few comments about the C++
1276        wrapper.
1279    Version 6.0 07-Jun-05
1280    ---------------------
1282     1. Some minor internal re-organization to help with my DFA experiments.
1284     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
1285        didn't matter for the library itself when fully configured, but did matter
1286        when compiling without UCP support, or within Exim, where the ucp files are
1287        not imported.
1289     3. Refactoring of the library code to split up the various functions into
1290        different source modules. The addition of the new DFA matching code (see
1291        below) to a single monolithic source would have made it really too
1292        unwieldy, quite apart from causing all the code to be include in a
1293        statically linked application, when only some functions are used. This is
1294        relevant even without the DFA addition now that patterns can be compiled in
1295        one application and matched in another.
1297        The downside of splitting up is that there have to be some external
1298        functions and data tables that are used internally in different modules of
1299        the library but which are not part of the API. These have all had their
1300        names changed to start with "_pcre_" so that they are unlikely to clash
1301        with other external names.
1303     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
1304        a different (DFA) algorithm. Although it is slower than the original
1305        function, it does have some advantages for certain types of matching
1306        problem.
1308     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
1309        including restarting after a partial match.
1311     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
1312        defined when compiling for Windows was sent to me. I have put it into the
1313        code, though I have no means of testing or verifying it.
1315     7. Added the pcre_refcount() auxiliary function.
1317     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
1318        match before or at the first newline in the subject string. In pcretest,
1319        the /f option on a pattern can be used to set this.
1321     9. A repeated \w when used in UTF-8 mode with characters greater than 256
1322        would behave wrongly. This has been present in PCRE since release 4.0.
1324    10. A number of changes to the pcregrep command:
1326        (a) Refactored how -x works; insert ^(...)$ instead of setting
1327            PCRE_ANCHORED and checking the length, in preparation for adding
1328            something similar for -w.
1330        (b) Added the -w (match as a word) option.
1332        (c) Refactored the way lines are read and buffered so as to have more
1333            than one at a time available.
1335        (d) Implemented a pcregrep test script.
1337        (e) Added the -M (multiline match) option. This allows patterns to match
1338            over several lines of the subject. The buffering ensures that at least
1339            8K, or the rest of the document (whichever is the shorter) is available
1340            for matching (and similarly the previous 8K for lookbehind assertions).
1342        (f) Changed the --help output so that it now says
1344              -w, --word-regex(p)
1346            instead of two lines, one with "regex" and the other with "regexp"
1347            because that confused at least one person since the short forms are the
1348            same. (This required a bit of code, as the output is generated
1349            automatically from a table. It wasn't just a text change.)
1351        (g) -- can be used to terminate pcregrep options if the next thing isn't an
1352            option but starts with a hyphen. Could be a pattern or a path name
1353            starting with a hyphen, for instance.
1355        (h) "-" can be given as a file name to represent stdin.
1357        (i) When file names are being printed, "(standard input)" is used for
1358            the standard input, for compatibility with GNU grep. Previously
1359            "<stdin>" was used.
1361        (j) The option --label=xxx can be used to supply a name to be used for
1362            stdin when file names are being printed. There is no short form.
1364        (k) Re-factored the options decoding logic because we are going to add
1365            two more options that take data. Such options can now be given in four
1366            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
1368        (l) Added the -A, -B, and -C options for requesting that lines of context
1369            around matches be printed.
1371        (m) Added the -L option to print the names of files that do not contain
1372            any matching lines, that is, the complement of -l.
1374        (n) The return code is 2 if any file cannot be opened, but pcregrep does
1375            continue to scan other files.
1377        (o) The -s option was incorrectly implemented. For compatibility with other
1378            greps, it now suppresses the error message for a non-existent or non-
1379            accessible file (but not the return code). There is a new option called
1380            -q that suppresses the output of matching lines, which was what -s was
1381            previously doing.
1383        (p) Added --include and --exclude options to specify files for inclusion
1384            and exclusion when recursing.
1386    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
1387        Hopefully, it now does.
1389    12. Missing cast in pcre_study().
1391    13. Added an "uninstall" target to the makefile.
1393    14. Replaced "extern" in the function prototypes in Makefile.in with
1394        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
1395        world, but is set differently for Windows.
1397    15. Added a second compiling function called pcre_compile2(). The only
1398        difference is that it has an extra argument, which is a pointer to an
1399        integer error code. When there is a compile-time failure, this is set
1400        non-zero, in addition to the error test pointer being set to point to an
1401        error message. The new argument may be NULL if no error number is required
1402        (but then you may as well call pcre_compile(), which is now just a
1403        wrapper). This facility is provided because some applications need a
1404        numeric error indication, but it has also enabled me to tidy up the way
1405        compile-time errors are handled in the POSIX wrapper.
1407    16. Added VPATH=.libs to the makefile; this should help when building with one
1408        prefix path and installing with another. (Or so I'm told by someone who
1409        knows more about this stuff than I do.)
1411    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
1412        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
1413        match everything, including newlines. This is not POSIX-compatible, but
1414        somebody wanted the feature. From pcretest it can be activated by using
1415        both the P and the s flags.
1417    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
1419    19. libpcre.pc was being incorrectly installed as executable.
1421    20. A couple of places in pcretest check for end-of-line by looking for '\n';
1422        it now also looks for '\r' so that it will work unmodified on Windows.
1424    21. Added Google's contributed C++ wrapper to the distribution.
1426    22. Added some untidy missing memory free() calls in pcretest, to keep
1427        Electric Fence happy when testing.
1431  Version 5.0 13-Sep-04  Version 5.0 13-Sep-04
1432  ---------------------  ---------------------

Removed from v.75  
changed lines
  Added in v.268

  ViewVC Help
Powered by ViewVC 1.1.5