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

Diff of /code/trunk/ChangeLog

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

revision 91 by nigel, Sat Feb 24 21:41:34 2007 UTC revision 365 by ph10, Fri Jul 11 17:06:55 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 8.0 02 Jul-08
5    ---------------------
6    
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).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
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.
20    
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.
24    
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.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
48    
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
50    
51        This potential security problem was recorded as CVE-2008-2371.
52    
53    12. For a pattern where the match had to start at the beginning or immediately
54        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
55        pcre_dfa_exec() could read past the end of the passed subject if there was
56        no match. To help with detecting such bugs (e.g. with valgrind), I modified
57        pcretest so that it places the subject at the end of its malloc-ed buffer.
58    
59    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
60        exec() might read past the end of the data buffer in UTF-8 mode.
61    
62    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
63        the data contained the byte 0x85 as part of a UTF-8 character within its
64        first line. This applied both to normal and DFA matching.
65    
66    
67    Version 7.7 07-May-08
68    ---------------------
69    
70    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
71        a string to a long long, pretend we don't even have a long long." This is
72        done by checking for the strtoq, strtoll, and _strtoi64 functions.
73    
74    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
75        pre-7.6 versions, which defined a global no_arg variable instead of putting
76        it in the RE class. (See also #8 below.)
77    
78    3.  Remove a line of dead code, identified by coverity and reported by Nuno
79        Lopes.
80    
81    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
82    
83        (1) The include/exclude patterns were being applied to the whole pathnames
84            of files, instead of just to the final components.
85    
86        (2) If there was more than one level of directory, the subdirectories were
87            skipped unless they satisfied the include/exclude conditions. This is
88            inconsistent with GNU grep (and could even be seen as contrary to the
89            pcregrep specification - which I improved to make it absolutely clear).
90            The action now is always to scan all levels of directory, and just
91            apply the include/exclude patterns to regular files.
92    
93    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
94        --exclude_dir in the tests to avoid scanning .svn directories.
95    
96    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
97        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
98        doesn't support NULs in patterns.
99    
100    7.  Added some missing "const"s to declarations of static tables in
101        pcre_compile.c and pcre_dfa_exec.c.
102    
103    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
104        caused by fix #2  above. (Subsequently also a second patch to fix the
105        first patch. And a third patch - this was a messy problem.)
106    
107    9.  Applied Craig's patch to remove the use of push_back().
108    
109    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
110        matching function regexec().
111    
112    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
113        which, however, unlike Perl's \g{...}, are subroutine calls, not back
114        references. PCRE supports relative numbers with this syntax (I don't think
115        Oniguruma does).
116    
117    12. Previously, a group with a zero repeat such as (...){0} was completely
118        omitted from the compiled regex. However, this means that if the group
119        was called as a subroutine from elsewhere in the pattern, things went wrong
120        (an internal error was given). Such groups are now left in the compiled
121        pattern, with a new opcode that causes them to be skipped at execution
122        time.
123    
124    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
125        to the way PCRE behaves:
126    
127        (a) A lone ] character is dis-allowed (Perl treats it as data).
128    
129        (b) A back reference to an unmatched subpattern matches an empty string
130            (Perl fails the current match path).
131    
132        (c) A data ] in a character class must be notated as \] because if the
133            first data character in a class is ], it defines an empty class. (In
134            Perl it is not possible to have an empty class.) The empty class []
135            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
136            The negative empty class [^] matches any one character, independently
137            of the DOTALL setting.
138    
139    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
140        non-existent subpattern following a character class starting with ']' and
141        containing () gave an internal compiling error instead of "reference to
142        non-existent subpattern". Fortunately, when the pattern did exist, the
143        compiled code was correct. (When scanning forwards to check for the
144        existencd of the subpattern, it was treating the data ']' as terminating
145        the class, so got the count wrong. When actually compiling, the reference
146        was subsequently set up correctly.)
147    
148    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
149        it was being rejected as not supported by pcre_dfa_exec(), even though
150        other assertions are supported. I have made pcre_dfa_exec() support
151        (*FAIL).
152    
153    16. The implementation of 13c above involved the invention of a new opcode,
154        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
155        cannot be changed at match time, I realized I could make a small
156        improvement to matching performance by compiling OP_ALLANY instead of
157        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
158        on the OP_ANY path.
159    
160    17. Compiling pcretest on Windows with readline support failed without the
161        following two fixes: (1) Make the unistd.h include conditional on
162        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
163    
164    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
165        ncurses library to be included for pcretest when ReadLine support is
166        requested, but also to allow for it to be overridden. This patch came from
167        Daniel Bergström.
168    
169    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
170        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
171        any errors with the current Unicode tables. Thanks to Peter Kankowski for
172        spotting this.
173    
174    
175    Version 7.6 28-Jan-08
176    ---------------------
177    
178    1.  A character class containing a very large number of characters with
179        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
180        overflow.
181    
182    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
183        HAVE_LONG_LONG is not defined.
184    
185    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
186        bring them up to date and include new features. This patch includes:
187    
188        - Fixed PH's badly added libz and libbz2 support.
189        - Fixed a problem with static linking.
190        - Added pcredemo. [But later removed - see 7 below.]
191        - Fixed dftables problem and added an option.
192        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
193            HAVE_LONG_LONG.
194        - Added readline support for pcretest.
195        - Added an listing of the option settings after cmake has run.
196    
197    4.  A user submitted a patch to Makefile that makes it easy to create
198        "pcre.dll" under mingw when using Configure/Make. I added stuff to
199        Makefile.am that cause it to include this special target, without
200        affecting anything else. Note that the same mingw target plus all
201        the other distribution libraries and programs are now supported
202        when configuring with CMake (see 6 below) instead of with
203        Configure/Make.
204    
205    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
206        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
207        exported in the Windows port". It has not yet been confirmed that the patch
208        solves the problem, but it does no harm.
209    
210    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
211        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
212        with CMake, and also correct the comment about stack recursion.
213    
214    7.  Remove the automatic building of pcredemo from the ./configure system and
215        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
216        of a program that users should build themselves after PCRE is installed, so
217        building it automatically is not really right. What is more, it gave
218        trouble in some build environments.
219    
220    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
221    
222    
223    Version 7.5 10-Jan-08
224    ---------------------
225    
226    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
227        values in parens when parsing an RE using the C++ wrapper."
228    
229    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
230        Characters greater than 255 were excluded from the class instead of being
231        included.
232    
233    3.  The same bug as (2) above applied to negated POSIX classes such as
234        [:^space:].
235    
236    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
237        defined or documented. It seems to have been a typo for PCRE_STATIC, so
238        I have changed it.
239    
240    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
241        first named subpattern) and a construct such as (?&a) would reference the
242        first named subpattern whose name started with "a" (in other words, the
243        length check was missing). Both these problems are fixed. "Subpattern name
244        expected" is now given for (?&) (a zero-length name), and this patch also
245        makes it give the same error for \k'' (previously it complained that that
246        was a reference to a non-existent subpattern).
247    
248    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
249        this is right because (?- can be followed by option settings as well as by
250        digits. I have, however, made the messages clearer.
251    
252    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
253        than the number used in the conditional) now cause a compile-time error.
254        This is actually not compatible with Perl, which accepts such patterns, but
255        treats the conditional as always being FALSE (as PCRE used to), but it
256        seems to me that giving a diagnostic is better.
257    
258    8.  Change "alphameric" to the more common word "alphanumeric" in comments
259        and messages.
260    
261    9.  Fix two occurrences of "backslash" in comments that should have been
262        "backspace".
263    
264    10. Remove two redundant lines of code that can never be obeyed (their function
265        was moved elsewhere).
266    
267    11. The program that makes PCRE's Unicode character property table had a bug
268        which caused it to generate incorrect table entries for sequences of
269        characters that have the same character type, but are in different scripts.
270        It amalgamated them into a single range, with the script of the first of
271        them. In other words, some characters were in the wrong script. There were
272        thirteen such cases, affecting characters in the following ranges:
273    
274          U+002b0 - U+002c1
275          U+0060c - U+0060d
276          U+0061e - U+00612
277          U+0064b - U+0065e
278          U+0074d - U+0076d
279          U+01800 - U+01805
280          U+01d00 - U+01d77
281          U+01d9b - U+01dbf
282          U+0200b - U+0200f
283          U+030fc - U+030fe
284          U+03260 - U+0327f
285          U+0fb46 - U+0fbb1
286          U+10450 - U+1049d
287    
288    12. The -o option (show only the matching part of a line) for pcregrep was not
289        compatible with GNU grep in that, if there was more than one match in a
290        line, it showed only the first of them. It now behaves in the same way as
291        GNU grep.
292    
293    13. If the -o and -v options were combined for pcregrep, it printed a blank
294        line for every non-matching line. GNU grep prints nothing, and pcregrep now
295        does the same. The return code can be used to tell if there were any
296        non-matching lines.
297    
298    14. Added --file-offsets and --line-offsets to pcregrep.
299    
300    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
301        infinitely looping recursion. The bug was that positive lookaheads were not
302        being skipped when checking for a possible empty match (negative lookaheads
303        and both kinds of lookbehind were skipped).
304    
305    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
306        inclusion of <windows.h> to before rather than after the definition of
307        INVALID_FILE_ATTRIBUTES (patch from David Byron).
308    
309    17. Specifying a possessive quantifier with a specific limit for a Unicode
310        character property caused pcre_compile() to compile bad code, which led at
311        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
312        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
313        caused the error; without that there was no problem.
314    
315    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
316    
317    19. Added --enable-pcretest-libreadline.
318    
319    20. In pcrecpp.cc, the variable 'count' was incremented twice in
320        RE::GlobalReplace(). As a result, the number of replacements returned was
321        double what it should be. I removed one of the increments, but Craig sent a
322        later patch that removed the other one (the right fix) and added unit tests
323        that check the return values (which was not done before).
324    
325    21. Several CMake things:
326    
327        (1) Arranged that, when cmake is used on Unix, the libraries end up with
328            the names libpcre and libpcreposix, not just pcre and pcreposix.
329    
330        (2) The above change means that pcretest and pcregrep are now correctly
331            linked with the newly-built libraries, not previously installed ones.
332    
333        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
334    
335    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
336        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
337        UTF-8 newline character). The key issue is that the pattern starts .*;
338        this means that the match must be either at the beginning, or after a
339        newline. The bug was in the code for advancing after a failed match and
340        checking that the new position followed a newline. It was not taking
341        account of UTF-8 characters correctly.
342    
343    23. PCRE was behaving differently from Perl in the way it recognized POSIX
344        character classes. PCRE was not treating the sequence [:...:] as a
345        character class unless the ... were all letters. Perl, however, seems to
346        allow any characters between [: and :], though of course it rejects as
347        unknown any "names" that contain non-letters, because all the known class
348        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
349        for example, whereas PCRE did not - it did not recognize a POSIX character
350        class. This seemed a bit dangerous, so the code has been changed to be
351        closer to Perl. The behaviour is not identical to Perl, because PCRE will
352        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
353        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
354        Perl does, and where it didn't before.
355    
356    24. Rewrite so as to remove the single use of %n from pcregrep because in some
357        Windows environments %n is disabled by default.
358    
359    
360    Version 7.4 21-Sep-07
361    ---------------------
362    
363    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
364        means that a class such as [\s] counted as "explicit reference to CR or
365        LF". That isn't really right - the whole point of the change was to try to
366        help when there was an actual mention of one of the two characters. So now
367        the change happens only if \r or \n (or a literal CR or LF) character is
368        encountered.
369    
370    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
371        of both had grown to the point where there were only 3 bits left.
372        Fortunately, there was spare space in the data structure, and so I have
373        moved the internal flags into a new 16-bit field to free up more option
374        bits.
375    
376    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
377        but did not set the internal JCHANGED flag - either of these is enough to
378        control the way the "get" function works - but the PCRE_INFO_JCHANGED
379        facility is supposed to tell if (?J) was ever used, so now (?J) at the
380        start sets both bits.
381    
382    4.  Added options (at build time, compile time, exec time) to change \R from
383        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
384    
385    5.  doc/pcresyntax.html was missing from the distribution.
386    
387    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
388        compatibility, even though it is no longer used.
389    
390    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
391        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
392        windows.h file is present (where different names are used). [This was
393        reversed later after testing - see 16 below.]
394    
395    8.  Changed all #include <config.h> to #include "config.h". There were also
396        some further <pcre.h> cases that I changed to "pcre.h".
397    
398    9.  When pcregrep was used with the --colour option, it missed the line ending
399        sequence off the lines that it output.
400    
401    10. It was pointed out to me that arrays of string pointers cause lots of
402        relocations when a shared library is dynamically loaded. A technique of
403        using a single long string with a table of offsets can drastically reduce
404        these. I have refactored PCRE in four places to do this. The result is
405        dramatic:
406    
407          Originally:                          290
408          After changing UCP table:            187
409          After changing error message table:   43
410          After changing table of "verbs"       36
411          After changing table of Posix names   22
412    
413        Thanks to the folks working on Gregex for glib for this insight.
414    
415    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
416        unicode-properties was also set.
417    
418    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
419    
420    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
421        checked only for CRLF.
422    
423    14. Added casts to pcretest.c to avoid compiler warnings.
424    
425    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
426    
427    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
428        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
429        entirely. This removes changes made in 7 above.
430    
431    17. The CMake files have been updated, and there is now more information about
432        building with CMake in the NON-UNIX-USE document.
433    
434    
435    Version 7.3 28-Aug-07
436    ---------------------
437    
438     1. In the rejigging of the build system that eventually resulted in 7.1, the
439        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
440        brackets there is not right, since it causes compilers to look for an
441        installed pcre.h, not the version that is in the source that is being
442        compiled (which of course may be different). I have changed it back to:
443    
444          #include "pcre.h"
445    
446        I have a vague recollection that the change was concerned with compiling in
447        different directories, but in the new build system, that is taken care of
448        by the VPATH setting the Makefile.
449    
450     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
451        when the subject happened to end in the byte 0x85 (e.g. if the last
452        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
453        characters but of course it shouldn't be taken as a newline when it is part
454        of another character. The bug was that, for an unlimited repeat of . in
455        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
456        characters when looking for a newline.
457    
458     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
459    
460     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
461        in debug output.
462    
463     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
464        long printing in the pcrecpp unittest when running under MinGW.
465    
466     6. ESC_K was left out of the EBCDIC table.
467    
468     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
469        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
470        limit also applies to "virtual nesting" when a pattern is recursive, and in
471        this case 1000 isn't so big. I have been able to remove this limit at the
472        expense of backing off one optimization in certain circumstances. Normally,
473        when pcre_exec() would call its internal match() function recursively and
474        immediately return the result unconditionally, it uses a "tail recursion"
475        feature to save stack. However, when a subpattern that can match an empty
476        string has an unlimited repetition quantifier, it no longer makes this
477        optimization. That gives it a stack frame in which to save the data for
478        checking that an empty string has been matched. Previously this was taken
479        from the 1000-entry workspace that had been reserved. So now there is no
480        explicit limit, but more stack is used.
481    
482     8. Applied Daniel's patches to solve problems with the import/export magic
483        syntax that is required for Windows, and which was going wrong for the
484        pcreposix and pcrecpp parts of the library. These were overlooked when this
485        problem was solved for the main library.
486    
487     9. There were some crude static tests to avoid integer overflow when computing
488        the size of patterns that contain repeated groups with explicit upper
489        limits. As the maximum quantifier is 65535, the maximum group length was
490        set at 30,000 so that the product of these two numbers did not overflow a
491        32-bit integer. However, it turns out that people want to use groups that
492        are longer than 30,000 bytes (though not repeat them that many times).
493        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
494        made it possible to implement the integer overflow checks in a much more
495        dynamic way, which I have now done. The artificial limitation on group
496        length has been removed - we now have only the limit on the total length of
497        the compiled pattern, which depends on the LINK_SIZE setting.
498    
499    10. Fixed a bug in the documentation for get/copy named substring when
500        duplicate names are permitted. If none of the named substrings are set, the
501        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
502        empty string.
503    
504    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
505        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
506        because the ] is interpreted as the first data character and the
507        terminating ] is not found. PCRE has been made compatible with Perl in this
508        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
509        cause memory overwriting.
510    
511    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
512        string has been matched (to stop an infinite loop). It was not recognizing
513        a conditional subpattern that could match an empty string if that
514        subpattern was within another subpattern. For example, it looped when
515        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
516        condition was not nested. This bug has been fixed.
517    
518    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
519        past the start of the subject in the presence of bytes with the top bit
520        set, for example "\x8aBCD".
521    
522    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
523        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
524    
525    14. Optimized (?!) to (*FAIL).
526    
527    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
528        This restricts code points to be within the range 0 to 0x10FFFF, excluding
529        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
530        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
531        does: it's just the validity check that is more restrictive.
532    
533    16. Inserted checks for integer overflows during escape sequence (backslash)
534        processing, and also fixed erroneous offset values for syntax errors during
535        backslash processing.
536    
537    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
538        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
539    
540    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
541        caused an overrun.
542    
543    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
544        something other than just ASCII characters) inside a group that had an
545        unlimited repeat caused a loop at compile time (while checking to see
546        whether the group could match an empty string).
547    
548    20. Debugging a pattern containing \p or \P could cause a crash. For example,
549        [\P{Any}] did so. (Error in the code for printing property names.)
550    
551    21. An orphan \E inside a character class could cause a crash.
552    
553    22. A repeated capturing bracket such as (A)? could cause a wild memory
554        reference during compilation.
555    
556    23. There are several functions in pcre_compile() that scan along a compiled
557        expression for various reasons (e.g. to see if it's fixed length for look
558        behind). There were bugs in these functions when a repeated \p or \P was
559        present in the pattern. These operators have additional parameters compared
560        with \d, etc, and these were not being taken into account when moving along
561        the compiled data. Specifically:
562    
563        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
564            length.
565    
566        (b) An item such as \pL+ within a repeated group could cause crashes or
567            loops.
568    
569        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
570            "reference to non-existent subpattern" error.
571    
572        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
573    
574    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
575        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
576    
577    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
578    
579    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
580        character were causing crashes (broken optimization).
581    
582    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
583        \p or \P) caused a compile-time loop.
584    
585    28. More problems have arisen in unanchored patterns when CRLF is a valid line
586        break. For example, the unstudied pattern [\r\n]A does not match the string
587        "\r\nA" because change 7.0/46 below moves the current point on by two
588        characters after failing to match at the start. However, the pattern \nA
589        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
590        the same is true. There doesn't seem any very clean way out of this, but
591        what I have chosen to do makes the common cases work: PCRE now takes note
592        of whether there can be an explicit match for \r or \n anywhere in the
593        pattern, and if so, 7.0/46 no longer applies. As part of this change,
594        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
595        pattern has explicit CR or LF references.
596    
597    29. Added (*CR) etc for changing newline setting at start of pattern.
598    
599    
600    Version 7.2 19-Jun-07
601    ---------------------
602    
603     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
604        which is apparently normally available under Windows.
605    
606     2. Re-jig the pcregrep tests with different newline settings in an attempt
607        to make them independent of the local environment's newline setting.
608    
609     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
610    
611     4. Some of the "internals" tests were previously cut out when the link size
612        was not 2, because the output contained actual offsets. The recent new
613        "Z" feature of pcretest means that these can be cut out, making the tests
614        usable with all link sizes.
615    
616     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
617        stack recursion. This gives a massive performance boost under BSD, but just
618        a small improvement under Linux. However, it saves one field in the frame
619        in all cases.
620    
621     6. Added more features from the forthcoming Perl 5.10:
622    
623        (a) (?-n) (where n is a string of digits) is a relative subroutine or
624            recursion call. It refers to the nth most recently opened parentheses.
625    
626        (b) (?+n) is also a relative subroutine call; it refers to the nth next
627            to be opened parentheses.
628    
629        (c) Conditions that refer to capturing parentheses can be specified
630            relatively, for example, (?(-2)... or (?(+3)...
631    
632        (d) \K resets the start of the current match so that everything before
633            is not part of it.
634    
635        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
636    
637        (f) \g{name} is another synonym - part of Perl 5.10's unification of
638            reference syntax.
639    
640        (g) (?| introduces a group in which the numbering of parentheses in each
641            alternative starts with the same number.
642    
643        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
644    
645     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
646        PCRE_INFO_JCHANGED.
647    
648     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
649        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
650        for detecting groups that can match an empty string.
651    
652     9. A pattern with a very large number of alternatives (more than several
653        hundred) was running out of internal workspace during the pre-compile
654        phase, where pcre_compile() figures out how much memory will be needed. A
655        bit of new cunning has reduced the workspace needed for groups with
656        alternatives. The 1000-alternative test pattern now uses 12 bytes of
657        workspace instead of running out of the 4096 that are available.
658    
659    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
660    
661    11. Applied patch from Google to remove an optimization that didn't quite work.
662        The report of the bug said:
663    
664          pcrecpp::RE("a*").FullMatch("aaa") matches, while
665          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
666          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
667    
668    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
669        it matched the wrong number of bytes.
670    
671    
672    Version 7.1 24-Apr-07
673    ---------------------
674    
675     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
676        that is more "standard", making use of automake and other Autotools. There
677        is some re-arrangement of the files and adjustment of comments consequent
678        on this.
679    
680     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
681        for recursive directory scanning broke on some systems because the files
682        are not scanned in any specific order and on different systems the order
683        was different. A call to "sort" has been inserted into RunGrepTest for the
684        approprate test as a short-term fix. In the longer term there may be an
685        alternative.
686    
687     3. I had an email from Eric Raymond about problems translating some of PCRE's
688        man pages to HTML (despite the fact that I distribute HTML pages, some
689        people do their own conversions for various reasons). The problems
690        concerned the use of low-level troff macros .br and .in. I have therefore
691        removed all such uses from the man pages (some were redundant, some could
692        be replaced by .nf/.fi pairs). The 132html script that I use to generate
693        HTML has been updated to handle .nf/.fi and to complain if it encounters
694        .br or .in.
695    
696     4. Updated comments in configure.ac that get placed in config.h.in and also
697        arranged for config.h to be included in the distribution, with the name
698        config.h.generic, for the benefit of those who have to compile without
699        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
700    
701     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
702        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
703        makevp.bat for the current PCRE, using the additional files
704        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
705    
706     6. A Windows user reported a minor discrepancy with test 2, which turned out
707        to be caused by a trailing space on an input line that had got lost in his
708        copy. The trailing space was an accident, so I've just removed it.
709    
710     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
711        that is needed.
712    
713     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
714        as "const" (a) because they are and (b) because it helps the PHP
715        maintainers who have recently made a script to detect big data structures
716        in the php code that should be moved to the .rodata section. I remembered
717        to update Builducptable as well, so it won't revert if ucptable.h is ever
718        re-created.
719    
720     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
721        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
722        order to be able to cut out the UTF-8 tables in the latter when UTF-8
723        support is not required. This saves 1.5-2K of code, which is important in
724        some applications.
725    
726        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
727        so as not to refer to the tables, even though these functions will never be
728        called when UTF-8 support is disabled. Otherwise there are problems with a
729        shared library.
730    
731    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
732    
733        (a) It was defining its arguments as char * instead of void *.
734    
735        (b) It was assuming that all moves were upwards in memory; this was true
736            a long time ago when I wrote it, but is no longer the case.
737    
738        The emulated memove() is provided for those environments that have neither
739        memmove() nor bcopy(). I didn't think anyone used it these days, but that
740        is clearly not the case, as these two bugs were recently reported.
741    
742    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
743        and Detrail to create the HTML documentation, the .txt form of the man
744        pages, and it removes trailing spaces from listed files. It also creates
745        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
746        case, it wraps all the #defines with #ifndefs. This script should be run
747        before "make dist".
748    
749    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
750        with Unicode property support.
751    
752        (a) For a maximizing quantifier, if the two different cases of the
753            character were of different lengths in their UTF-8 codings (there are
754            some cases like this - I found 11), and the matching function had to
755            back up over a mixture of the two cases, it incorrectly assumed they
756            were both the same length.
757    
758        (b) When PCRE was configured to use the heap rather than the stack for
759            recursion during matching, it was not correctly preserving the data for
760            the other case of a UTF-8 character when checking ahead for a match
761            while processing a minimizing repeat. If the check also involved
762            matching a wide character, but failed, corruption could cause an
763            erroneous result when trying to check for a repeat of the original
764            character.
765    
766    13. Some tidying changes to the testing mechanism:
767    
768        (a) The RunTest script now detects the internal link size and whether there
769            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
770            values substituted by "configure". (The RunGrepTest script already did
771            this for UTF-8.) The configure.ac script no longer substitutes the
772            relevant variables.
773    
774        (b) The debugging options /B and /D in pcretest show the compiled bytecode
775            with length and offset values. This means that the output is different
776            for different internal link sizes. Test 2 is skipped for link sizes
777            other than 2 because of this, bypassing the problem. Unfortunately,
778            there was also a test in test 3 (the locale tests) that used /B and
779            failed for link sizes other than 2. Rather than cut the whole test out,
780            I have added a new /Z option to pcretest that replaces the length and
781            offset values with spaces. This is now used to make test 3 independent
782            of link size. (Test 2 will be tidied up later.)
783    
784    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
785        segmentation fault instead of returning the appropriate error message.
786    
787    15. In multiline mode when the newline sequence was set to "any", the pattern
788        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
789        This doesn't seem right; it now treats the CRLF combination as the line
790        ending, and so does not match in that case. It's only a pattern such as ^$
791        that would hit this one: something like ^ABC$ would have failed after \r
792        and then tried again after \r\n.
793    
794    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
795        in an attempt to make files that differ only in their line terminators
796        compare equal. This works on Linux.
797    
798    17. Under certain error circumstances pcregrep might try to free random memory
799        as it exited. This is now fixed, thanks to valgrind.
800    
801    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
802        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
803        was because its rules for how to advance for /g after matching an empty
804        string at the end of a line did not allow for this case. They now check for
805        it specially.
806    
807    20. pcretest is supposed to handle patterns and data of any length, by
808        extending its buffers when necessary. It was getting this wrong when the
809        buffer for a data line had to be extended.
810    
811    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
812        CRLF as a newline sequence.
813    
814    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
815        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
816        I have nevertheless tidied it up.
817    
818    23. Added some casts to kill warnings from HP-UX ia64 compiler.
819    
820    24. Added a man page for pcre-config.
821    
822    
823    Version 7.0 19-Dec-06
824    ---------------------
825    
826     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
827        moving to gcc 4.1.1.
828    
829     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
830        sys/time.h, which is documented as needed for this function. It doesn't
831        seem to matter on Linux, but it showed up on some releases of OS X.
832    
833     3. It seems that there are systems where bytes whose values are greater than
834        127 match isprint() in the "C" locale. The "C" locale should be the
835        default when a C program starts up. In most systems, only ASCII printing
836        characters match isprint(). This difference caused the output from pcretest
837        to vary, making some of the tests fail. I have changed pcretest so that:
838    
839        (a) When it is outputting text in the compiled version of a pattern, bytes
840            other than 32-126 are always shown as hex escapes.
841    
842        (b) When it is outputting text that is a matched part of a subject string,
843            it does the same, unless a different locale has been set for the match
844            (using the /L modifier). In this case, it uses isprint() to decide.
845    
846     4. Fixed a major bug that caused incorrect computation of the amount of memory
847        required for a compiled pattern when options that changed within the
848        pattern affected the logic of the preliminary scan that determines the
849        length. The relevant options are -x, and -i in UTF-8 mode. The result was
850        that the computed length was too small. The symptoms of this bug were
851        either the PCRE error "internal error: code overflow" from pcre_compile(),
852        or a glibc crash with a message such as "pcretest: free(): invalid next
853        size (fast)". Examples of patterns that provoked this bug (shown in
854        pcretest format) are:
855    
856          /(?-x: )/x
857          /(?x)(?-x: \s*#\s*)/
858          /((?i)[\x{c0}])/8
859          /(?i:[\x{c0}])/8
860    
861        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
862        is now done differently.
863    
864     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
865        wrapper classes; (b) implement a new function in the C++ scanner that is
866        more efficient than the old way of doing things because it avoids levels of
867        recursion in the regex matching; (c) add a paragraph to the documentation
868        for the FullMatch() function.
869    
870     6. The escape sequence \n was being treated as whatever was defined as
871        "newline". Not only was this contrary to the documentation, which states
872        that \n is character 10 (hex 0A), but it also went horribly wrong when
873        "newline" was defined as CRLF. This has been fixed.
874    
875     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
876        was being set to -1 for the "end of line" case (supposedly a value that no
877        character can have). Though this value is never used (the check for end of
878        line is "zero bytes in current character"), it caused compiler complaints.
879        I've changed it to 0xffffffff.
880    
881     8. In pcre_version.c, the version string was being built by a sequence of
882        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
883        string (as it is for production releases) called a macro with an empty
884        argument. The C standard says the result of this is undefined. The gcc
885        compiler treats it as an empty string (which was what was wanted) but it is
886        reported that Visual C gives an error. The source has been hacked around to
887        avoid this problem.
888    
889     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
890        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
891        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
892        of them did).
893    
894    10. Originally, pcretest opened its input and output without "b"; then I was
895        told that "b" was needed in some environments, so it was added for release
896        5.0 to both the input and output. (It makes no difference on Unix-like
897        systems.) Later I was told that it is wrong for the input on Windows. I've
898        now abstracted the modes into two macros, to make it easier to fiddle with
899        them, and removed "b" from the input mode under Windows.
900    
901    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
902    
903    12. Added -help and --help to pcretest as an official way of being reminded
904        of the options.
905    
906    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
907        and pcrecpp.cc because they annoy compilers at high warning levels.
908    
909    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
910    
911    15. Fixed an occurrence of == in configure.ac that should have been = (shell
912        scripts are not C programs :-) and which was not noticed because it works
913        on Linux.
914    
915    16. pcretest is supposed to handle any length of pattern and data line (as one
916        line or as a continued sequence of lines) by extending its input buffer if
917        necessary. This feature was broken for very long pattern lines, leading to
918        a string of junk being passed to pcre_compile() if the pattern was longer
919        than about 50K.
920    
921    17. I have done a major re-factoring of the way pcre_compile() computes the
922        amount of memory needed for a compiled pattern. Previously, there was code
923        that made a preliminary scan of the pattern in order to do this. That was
924        OK when PCRE was new, but as the facilities have expanded, it has become
925        harder and harder to keep it in step with the real compile phase, and there
926        have been a number of bugs (see for example, 4 above). I have now found a
927        cunning way of running the real compile function in a "fake" mode that
928        enables it to compute how much memory it would need, while actually only
929        ever using a few hundred bytes of working memory and without too many
930        tests of the mode. This should make future maintenance and development
931        easier. A side effect of this work is that the limit of 200 on the nesting
932        depth of parentheses has been removed (though this was never a serious
933        limitation, I suspect). However, there is a downside: pcre_compile() now
934        runs more slowly than before (30% or more, depending on the pattern). I
935        hope this isn't a big issue. There is no effect on runtime performance.
936    
937    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
938        newline (only possible for the last line of a file) and it was a
939        pattern that set a locale (followed by /Lsomething), pcretest crashed.
940    
941    19. Added additional timing features to pcretest. (1) The -tm option now times
942        matching only, not compiling. (2) Both -t and -tm can be followed, as a
943        separate command line item, by a number that specifies the number of
944        repeats to use when timing. The default is 50000; this gives better
945        precision, but takes uncomfortably long for very large patterns.
946    
947    20. Extended pcre_study() to be more clever in cases where a branch of a
948        subpattern has no definite first character. For example, (a*|b*)[cd] would
949        previously give no result from pcre_study(). Now it recognizes that the
950        first character must be a, b, c, or d.
951    
952    21. There was an incorrect error "recursive call could loop indefinitely" if
953        a subpattern (or the entire pattern) that was being tested for matching an
954        empty string contained only one non-empty item after a nested subpattern.
955        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
956        incorrectly, because the \d was being skipped in the check.
957    
958    22. The pcretest program now has a new pattern option /B and a command line
959        option -b, which is equivalent to adding /B to every pattern. This causes
960        it to show the compiled bytecode, without the additional information that
961        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
962        is the same as /B/I).
963    
964    23. A new optimization is now able automatically to treat some sequences such
965        as a*b as a*+b. More specifically, if something simple (such as a character
966        or a simple class like \d) has an unlimited quantifier, and is followed by
967        something that cannot possibly match the quantified thing, the quantifier
968        is automatically "possessified".
969    
970    24. A recursive reference to a subpattern whose number was greater than 39
971        went wrong under certain circumstances in UTF-8 mode. This bug could also
972        have affected the operation of pcre_study().
973    
974    25. Realized that a little bit of performance could be had by replacing
975        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
976    
977    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
978    
979    27. Possessive quantifiers such as a++ were previously implemented by turning
980        them into atomic groups such as ($>a+). Now they have their own opcodes,
981        which improves performance. This includes the automatically created ones
982        from 23 above.
983    
984    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
985        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
986        the first matched character to be a colon. This applied both to named and
987        numbered groups.
988    
989    29. The ucpinternal.h header file was missing its idempotency #ifdef.
990    
991    30. I was sent a "project" file called libpcre.a.dev which I understand makes
992        building PCRE on Windows easier, so I have included it in the distribution.
993    
994    31. There is now a check in pcretest against a ridiculously large number being
995        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
996        loop, the loop is abandoned.
997    
998    32. Forward references to subpatterns in conditions such as (?(2)...) where
999        subpattern 2 is defined later cause pcre_compile() to search forwards in
1000        the pattern for the relevant set of parentheses. This search went wrong
1001        when there were unescaped parentheses in a character class, parentheses
1002        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
1003    
1004    33. "Subroutine" calls and backreferences were previously restricted to
1005        referencing subpatterns earlier in the regex. This restriction has now
1006        been removed.
1007    
1008    34. Added a number of extra features that are going to be in Perl 5.10. On the
1009        whole, these are just syntactic alternatives for features that PCRE had
1010        previously implemented using the Python syntax or my own invention. The
1011        other formats are all retained for compatibility.
1012    
1013        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
1014            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
1015            also .NET compatible.
1016    
1017        (b) A recursion or subroutine call to a named group can now be defined as
1018            (?&name) as well as (?P>name).
1019    
1020        (c) A backreference to a named group can now be defined as \k<name> or
1021            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1022            5.10, are also .NET compatible.
1023    
1024        (d) A conditional reference to a named group can now use the syntax
1025            (?(<name>) or (?('name') as well as (?(name).
1026    
1027        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1028            groups (named and numbered) that are never evaluated inline, but can be
1029            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1030            is always false. There may be only one alternative in such a group.
1031    
1032        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1033            as the simple (?(R). The condition is true only if the most recent
1034            recursion is that of the given number or name. It does not search out
1035            through the entire recursion stack.
1036    
1037        (g) The escape \gN or \g{N} has been added, where N is a positive or
1038            negative number, specifying an absolute or relative reference.
1039    
1040    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1041        some "unreachable code" warnings.
1042    
1043    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1044        things, this adds five new scripts.
1045    
1046    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1047        There were also incompatibilities regarding the handling of \Q..\E inside
1048        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1049        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1050    
1051    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1052        matches an empty string, and forcibly breaks the loop. There were bugs in
1053        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1054        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1055        separate and independent bugs (that affected different cases) have been
1056        fixed.
1057    
1058    39. Refactored the code to abolish the use of different opcodes for small
1059        capturing bracket numbers. This is a tidy that I avoided doing when I
1060        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1061        The new approach is not only tidier, it makes it possible to reduce the
1062        memory needed to fix the previous bug (38).
1063    
1064    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1065        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1066        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1067        mode.
1068    
1069    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1070        report.
1071    
1072    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1073        copy construction and assignment in the C++ wrapper.
1074    
1075    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1076        couple of bugs that could have given wrong results in the "--newline=crlf"
1077        case.
1078    
1079    44. Added a number of casts and did some reorganization of signed/unsigned int
1080        variables following suggestions from Dair Grant. Also renamed the variable
1081        "this" as "item" because it is a C++ keyword.
1082    
1083    45. Arranged for dftables to add
1084    
1085          #include "pcre_internal.h"
1086    
1087        to pcre_chartables.c because without it, gcc 4.x may remove the array
1088        definition from the final binary if PCRE is built into a static library and
1089        dead code stripping is activated.
1090    
1091    46. For an unanchored pattern, if a match attempt fails at the start of a
1092        newline sequence, and the newline setting is CRLF or ANY, and the next two
1093        characters are CRLF, advance by two characters instead of one.
1094    
1095    
1096  Version 6.7 04-Jul-06  Version 6.7 04-Jul-06
1097  ---------------------  ---------------------
1098    

Legend:
Removed from v.91  
changed lines
  Added in v.365

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12