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

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12