/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

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

Legend:
Removed from v.195  
changed lines
  Added in v.359

  ViewVC Help
Powered by ViewVC 1.1.5