ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.155  
changed lines
  Added in v.354

  ViewVC Help
Powered by ViewVC 1.1.5