/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.85  
changed lines
  Added in v.239

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12