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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.190  
changed lines
  Added in v.408

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12