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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.151  
changed lines
  Added in v.356

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12