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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.142  
changed lines
  Added in v.342

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12