ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5