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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.169  
changed lines
  Added in v.416

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12