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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.178  
changed lines
  Added in v.399

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12