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

Diff of /code/trunk/ChangeLog

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

revision 113 by ph10, Fri Mar 9 10:13:26 2007 UTC revision 295 by ph10, Mon Dec 31 17:00:24 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.1 05-Mar-07  Version 7.5 31-Dec-07
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
20    
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
28    
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
32    
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
44    
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
47    
48    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
54    
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
68    
69    12. The -o option (show only the matching part of a line) for pcregrep was not
70        compatible with GNU grep in that, if there was more than one match in a
71        line, it showed only the first of them. It now behaves in the same way as
72        GNU grep.
73    
74    13. If the -o and -v options were combined for pcregrep, it printed a blank
75        line for every non-matching line. GNU grep prints nothing, and pcregrep now
76        does the same. The return code can be used to tell if there were any
77        non-matching lines.
78    
79    14. Added --file-offsets and --line-offsets to pcregrep.
80    
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82        infinitely looping recursion. The bug was that positive lookaheads were not
83        being skipped when checking for a possible empty match (negative lookaheads
84        and both kinds of lookbehind were skipped).
85    
86    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87        inclusion of <windows.h> to before rather than after the definition of
88        INVALID_FILE_ATTRIBUTES (patch from David Byron).
89    
90    17. Specifying a possessive quantifier with a specific limit for a Unicode
91        character property caused pcre_compile() to compile bad code, which led at
92        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94        caused the error; without that there was no problem.
95    
96    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
97    
98    19. Added --enable-pcretest-libreadline.
99    
100    20. In pcrecpp.cc, the variable 'count' was incremented twice in
101        RE::GlobalReplace(). As a result, the number of replacements returned was
102        double what it should be. I have removed one of the increments.
103    
104    21. Several CMake things:
105    
106        (1) Arranged that, when cmake is used on Unix, the libraries end up with
107            the names libpcre and libpcreposix, not just pcre and pcreposix.
108    
109        (2) The above change means that pcretest and pcregrep are now correctly
110            linked with the newly-built libraries, not previously installed ones.
111    
112        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
113    
114    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
115        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
116        UTF-8 newline character). The key issue is that the pattern starts .*;
117        this means that the match must be either at the beginning, or after a
118        newline. The bug was in the code for advancing after a failed match and
119        checking that the new position followed a newline. It was not taking
120        account of UTF-8 characters correctly.
121    
122    23. PCRE was behaving differently from Perl in the way it recognized POSIX
123        character classes. PCRE was not treating the sequence [:...:] as a
124        character class unless the ... were all letters. Perl, however, seems to
125        allow any characters between [: and :], though of course it rejects as
126        unknown any "names" that contain non-letters, because all the known class
127        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
128        for example, whereas PCRE did not - it did not recognize a POSIX character
129        class. This seemed a bit dangerous, so the code has been changed to be
130        closer to Perl. The behaviour is not identical to Perl, because PCRE will
131        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
132        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
133        Perl does, and where it didn't before.
134    
135    
136    Version 7.4 21-Sep-07
137    ---------------------
138    
139    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
140        means that a class such as [\s] counted as "explicit reference to CR or
141        LF". That isn't really right - the whole point of the change was to try to
142        help when there was an actual mention of one of the two characters. So now
143        the change happens only if \r or \n (or a literal CR or LF) character is
144        encountered.
145    
146    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
147        of both had grown to the point where there were only 3 bits left.
148        Fortunately, there was spare space in the data structure, and so I have
149        moved the internal flags into a new 16-bit field to free up more option
150        bits.
151    
152    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
153        but did not set the internal JCHANGED flag - either of these is enough to
154        control the way the "get" function works - but the PCRE_INFO_JCHANGED
155        facility is supposed to tell if (?J) was ever used, so now (?J) at the
156        start sets both bits.
157    
158    4.  Added options (at build time, compile time, exec time) to change \R from
159        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
160    
161    5.  doc/pcresyntax.html was missing from the distribution.
162    
163    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
164        compatibility, even though it is no longer used.
165    
166    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
167        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
168        windows.h file is present (where different names are used). [This was
169        reversed later after testing - see 16 below.]
170    
171    8.  Changed all #include <config.h> to #include "config.h". There were also
172        some further <pcre.h> cases that I changed to "pcre.h".
173    
174    9.  When pcregrep was used with the --colour option, it missed the line ending
175        sequence off the lines that it output.
176    
177    10. It was pointed out to me that arrays of string pointers cause lots of
178        relocations when a shared library is dynamically loaded. A technique of
179        using a single long string with a table of offsets can drastically reduce
180        these. I have refactored PCRE in four places to do this. The result is
181        dramatic:
182    
183          Originally:                          290
184          After changing UCP table:            187
185          After changing error message table:   43
186          After changing table of "verbs"       36
187          After changing table of Posix names   22
188    
189        Thanks to the folks working on Gregex for glib for this insight.
190    
191    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
192        unicode-properties was also set.
193    
194    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
195    
196    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
197        checked only for CRLF.
198    
199    14. Added casts to pcretest.c to avoid compiler warnings.
200    
201    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
202    
203    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
204        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
205        entirely. This removes changes made in 7 above.
206    
207    17. The CMake files have been updated, and there is now more information about
208        building with CMake in the NON-UNIX-USE document.
209    
210    
211    Version 7.3 28-Aug-07
212    ---------------------
213    
214     1. In the rejigging of the build system that eventually resulted in 7.1, the
215        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
216        brackets there is not right, since it causes compilers to look for an
217        installed pcre.h, not the version that is in the source that is being
218        compiled (which of course may be different). I have changed it back to:
219    
220          #include "pcre.h"
221    
222        I have a vague recollection that the change was concerned with compiling in
223        different directories, but in the new build system, that is taken care of
224        by the VPATH setting the Makefile.
225    
226     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
227        when the subject happened to end in the byte 0x85 (e.g. if the last
228        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
229        characters but of course it shouldn't be taken as a newline when it is part
230        of another character. The bug was that, for an unlimited repeat of . in
231        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
232        characters when looking for a newline.
233    
234     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
235    
236     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
237        in debug output.
238    
239     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
240        long printing in the pcrecpp unittest when running under MinGW.
241    
242     6. ESC_K was left out of the EBCDIC table.
243    
244     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
245        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
246        limit also applies to "virtual nesting" when a pattern is recursive, and in
247        this case 1000 isn't so big. I have been able to remove this limit at the
248        expense of backing off one optimization in certain circumstances. Normally,
249        when pcre_exec() would call its internal match() function recursively and
250        immediately return the result unconditionally, it uses a "tail recursion"
251        feature to save stack. However, when a subpattern that can match an empty
252        string has an unlimited repetition quantifier, it no longer makes this
253        optimization. That gives it a stack frame in which to save the data for
254        checking that an empty string has been matched. Previously this was taken
255        from the 1000-entry workspace that had been reserved. So now there is no
256        explicit limit, but more stack is used.
257    
258     8. Applied Daniel's patches to solve problems with the import/export magic
259        syntax that is required for Windows, and which was going wrong for the
260        pcreposix and pcrecpp parts of the library. These were overlooked when this
261        problem was solved for the main library.
262    
263     9. There were some crude static tests to avoid integer overflow when computing
264        the size of patterns that contain repeated groups with explicit upper
265        limits. As the maximum quantifier is 65535, the maximum group length was
266        set at 30,000 so that the product of these two numbers did not overflow a
267        32-bit integer. However, it turns out that people want to use groups that
268        are longer than 30,000 bytes (though not repeat them that many times).
269        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
270        made it possible to implement the integer overflow checks in a much more
271        dynamic way, which I have now done. The artificial limitation on group
272        length has been removed - we now have only the limit on the total length of
273        the compiled pattern, which depends on the LINK_SIZE setting.
274    
275    10. Fixed a bug in the documentation for get/copy named substring when
276        duplicate names are permitted. If none of the named substrings are set, the
277        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
278        empty string.
279    
280    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
281        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
282        because the ] is interpreted as the first data character and the
283        terminating ] is not found. PCRE has been made compatible with Perl in this
284        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
285        cause memory overwriting.
286    
287    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
288        string has been matched (to stop an infinite loop). It was not recognizing
289        a conditional subpattern that could match an empty string if that
290        subpattern was within another subpattern. For example, it looped when
291        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
292        condition was not nested. This bug has been fixed.
293    
294    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
295        past the start of the subject in the presence of bytes with the top bit
296        set, for example "\x8aBCD".
297    
298    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
299        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
300    
301    14. Optimized (?!) to (*FAIL).
302    
303    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
304        This restricts code points to be within the range 0 to 0x10FFFF, excluding
305        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
306        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
307        does: it's just the validity check that is more restrictive.
308    
309    16. Inserted checks for integer overflows during escape sequence (backslash)
310        processing, and also fixed erroneous offset values for syntax errors during
311        backslash processing.
312    
313    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
314        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
315    
316    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
317        caused an overrun.
318    
319    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
320        something other than just ASCII characters) inside a group that had an
321        unlimited repeat caused a loop at compile time (while checking to see
322        whether the group could match an empty string).
323    
324    20. Debugging a pattern containing \p or \P could cause a crash. For example,
325        [\P{Any}] did so. (Error in the code for printing property names.)
326    
327    21. An orphan \E inside a character class could cause a crash.
328    
329    22. A repeated capturing bracket such as (A)? could cause a wild memory
330        reference during compilation.
331    
332    23. There are several functions in pcre_compile() that scan along a compiled
333        expression for various reasons (e.g. to see if it's fixed length for look
334        behind). There were bugs in these functions when a repeated \p or \P was
335        present in the pattern. These operators have additional parameters compared
336        with \d, etc, and these were not being taken into account when moving along
337        the compiled data. Specifically:
338    
339        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
340            length.
341    
342        (b) An item such as \pL+ within a repeated group could cause crashes or
343            loops.
344    
345        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
346            "reference to non-existent subpattern" error.
347    
348        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
349    
350    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
351        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
352    
353    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
354    
355    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
356        character were causing crashes (broken optimization).
357    
358    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
359        \p or \P) caused a compile-time loop.
360    
361    28. More problems have arisen in unanchored patterns when CRLF is a valid line
362        break. For example, the unstudied pattern [\r\n]A does not match the string
363        "\r\nA" because change 7.0/46 below moves the current point on by two
364        characters after failing to match at the start. However, the pattern \nA
365        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
366        the same is true. There doesn't seem any very clean way out of this, but
367        what I have chosen to do makes the common cases work: PCRE now takes note
368        of whether there can be an explicit match for \r or \n anywhere in the
369        pattern, and if so, 7.0/46 no longer applies. As part of this change,
370        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
371        pattern has explicit CR or LF references.
372    
373    29. Added (*CR) etc for changing newline setting at start of pattern.
374    
375    
376    Version 7.2 19-Jun-07
377    ---------------------
378    
379     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
380        which is apparently normally available under Windows.
381    
382     2. Re-jig the pcregrep tests with different newline settings in an attempt
383        to make them independent of the local environment's newline setting.
384    
385     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
386    
387     4. Some of the "internals" tests were previously cut out when the link size
388        was not 2, because the output contained actual offsets. The recent new
389        "Z" feature of pcretest means that these can be cut out, making the tests
390        usable with all link sizes.
391    
392     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
393        stack recursion. This gives a massive performance boost under BSD, but just
394        a small improvement under Linux. However, it saves one field in the frame
395        in all cases.
396    
397     6. Added more features from the forthcoming Perl 5.10:
398    
399        (a) (?-n) (where n is a string of digits) is a relative subroutine or
400            recursion call. It refers to the nth most recently opened parentheses.
401    
402        (b) (?+n) is also a relative subroutine call; it refers to the nth next
403            to be opened parentheses.
404    
405        (c) Conditions that refer to capturing parentheses can be specified
406            relatively, for example, (?(-2)... or (?(+3)...
407    
408        (d) \K resets the start of the current match so that everything before
409            is not part of it.
410    
411        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
412    
413        (f) \g{name} is another synonym - part of Perl 5.10's unification of
414            reference syntax.
415    
416        (g) (?| introduces a group in which the numbering of parentheses in each
417            alternative starts with the same number.
418    
419        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
420    
421     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
422        PCRE_INFO_JCHANGED.
423    
424     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
425        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
426        for detecting groups that can match an empty string.
427    
428     9. A pattern with a very large number of alternatives (more than several
429        hundred) was running out of internal workspace during the pre-compile
430        phase, where pcre_compile() figures out how much memory will be needed. A
431        bit of new cunning has reduced the workspace needed for groups with
432        alternatives. The 1000-alternative test pattern now uses 12 bytes of
433        workspace instead of running out of the 4096 that are available.
434    
435    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
436    
437    11. Applied patch from Google to remove an optimization that didn't quite work.
438        The report of the bug said:
439    
440          pcrecpp::RE("a*").FullMatch("aaa") matches, while
441          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
442          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
443    
444    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
445        it matched the wrong number of bytes.
446    
447    
448    Version 7.1 24-Apr-07
449  ---------------------  ---------------------
450    
451   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
452      that is more "standard", making use of automake and other autotools. There      that is more "standard", making use of automake and other Autotools. There
453      is some re-arrangement of the files and adjustment of comments consequent      is some re-arrangement of the files and adjustment of comments consequent
454      on this.      on this.
455    
# Line 26  Version 7.1 05-Mar-07 Line 470  Version 7.1 05-Mar-07
470      .br or .in.      .br or .in.
471    
472   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
473      arranged for config.h to be included in the distribution, with the name      arranged for config.h to be included in the distribution, with the name
474      config.h.generic, for the benefit of those who have to compile without      config.h.generic, for the benefit of those who have to compile without
475      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
476    
477   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
478      Weber: (1) pcre_internal.h was missing some function renames; (2) updated      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
479      makevp.bat for the current PCRE, using the additional files !compile.txt,      makevp.bat for the current PCRE, using the additional files
480      !linklib.txt, and pcregexp.pas.      makevp_c.txt, makevp_l.txt, and pcregexp.pas.
481    
482   6. A Windows user reported a minor discrepancy with test 2, which turned out   6. A Windows user reported a minor discrepancy with test 2, which turned out
483      to be caused by a trailing space on an input line that had got lost in his      to be caused by a trailing space on an input line that had got lost in his
# Line 60  Version 7.1 05-Mar-07 Line 504  Version 7.1 05-Mar-07
504      called when UTF-8 support is disabled. Otherwise there are problems with a      called when UTF-8 support is disabled. Otherwise there are problems with a
505      shared library.      shared library.
506    
507  10. The emulated memmove() function in pcre_internal.h (provided for those  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
508      environments that have neither memmove() nor bcopy()) was defining its  
509      arguments as char * instead of void *.      (a) It was defining its arguments as char * instead of void *.
510    
511        (b) It was assuming that all moves were upwards in memory; this was true
512            a long time ago when I wrote it, but is no longer the case.
513    
514        The emulated memove() is provided for those environments that have neither
515        memmove() nor bcopy(). I didn't think anyone used it these days, but that
516        is clearly not the case, as these two bugs were recently reported.
517    
518  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
519      and Detrail to create the HTML documentation, the .txt form of the man      and Detrail to create the HTML documentation, the .txt form of the man
520      pages, and it removes trailing spaces from listed files. It also creates      pages, and it removes trailing spaces from listed files. It also creates
521      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
522      case, it wraps all the #defines with #ifndefs. This script should be run      case, it wraps all the #defines with #ifndefs. This script should be run
523      before "make dist".      before "make dist".
524    
525    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
526        with Unicode property support.
527    
528        (a) For a maximizing quantifier, if the two different cases of the
529            character were of different lengths in their UTF-8 codings (there are
530            some cases like this - I found 11), and the matching function had to
531            back up over a mixture of the two cases, it incorrectly assumed they
532            were both the same length.
533    
534        (b) When PCRE was configured to use the heap rather than the stack for
535            recursion during matching, it was not correctly preserving the data for
536            the other case of a UTF-8 character when checking ahead for a match
537            while processing a minimizing repeat. If the check also involved
538            matching a wide character, but failed, corruption could cause an
539            erroneous result when trying to check for a repeat of the original
540            character.
541    
542    13. Some tidying changes to the testing mechanism:
543    
544        (a) The RunTest script now detects the internal link size and whether there
545            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
546            values substituted by "configure". (The RunGrepTest script already did
547            this for UTF-8.) The configure.ac script no longer substitutes the
548            relevant variables.
549    
550        (b) The debugging options /B and /D in pcretest show the compiled bytecode
551            with length and offset values. This means that the output is different
552            for different internal link sizes. Test 2 is skipped for link sizes
553            other than 2 because of this, bypassing the problem. Unfortunately,
554            there was also a test in test 3 (the locale tests) that used /B and
555            failed for link sizes other than 2. Rather than cut the whole test out,
556            I have added a new /Z option to pcretest that replaces the length and
557            offset values with spaces. This is now used to make test 3 independent
558            of link size. (Test 2 will be tidied up later.)
559    
560    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
561        segmentation fault instead of returning the appropriate error message.
562    
563    15. In multiline mode when the newline sequence was set to "any", the pattern
564        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
565        This doesn't seem right; it now treats the CRLF combination as the line
566        ending, and so does not match in that case. It's only a pattern such as ^$
567        that would hit this one: something like ^ABC$ would have failed after \r
568        and then tried again after \r\n.
569    
570    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
571        in an attempt to make files that differ only in their line terminators
572        compare equal. This works on Linux.
573    
574    17. Under certain error circumstances pcregrep might try to free random memory
575        as it exited. This is now fixed, thanks to valgrind.
576    
577    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
578        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
579        was because its rules for how to advance for /g after matching an empty
580        string at the end of a line did not allow for this case. They now check for
581        it specially.
582    
583    20. pcretest is supposed to handle patterns and data of any length, by
584        extending its buffers when necessary. It was getting this wrong when the
585        buffer for a data line had to be extended.
586    
587    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
588        CRLF as a newline sequence.
589    
590    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
591        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
592        I have nevertheless tidied it up.
593    
594    23. Added some casts to kill warnings from HP-UX ia64 compiler.
595    
596    24. Added a man page for pcre-config.
597    
598    
599  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
600  ---------------------  ---------------------

Legend:
Removed from v.113  
changed lines
  Added in v.295

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12