ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.169  
changed lines
  Added in v.355

  ViewVC Help
Powered by ViewVC 1.1.5