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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.81  
changed lines
  Added in v.236

  ViewVC Help
Powered by ViewVC 1.1.5