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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.96  
changed lines
  Added in v.409

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12