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

Diff of /code/trunk/ChangeLog

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

revision 161 by ph10, Thu May 3 10:28:07 2007 UTC revision 475 by ph10, Sat Jan 2 18:21:30 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.2 01-May-07  Version 8.01 11-Dec-09
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
18    
19    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
20        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
21        assertion pattern did not match (meaning that the assertion was true), it
22        was incorrectly treated as false if the SKIP had been reached during the
23        matching. This also applied to assertions used as conditions.
24    
25    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
26        assertion subpattern, including such a pattern used as a condition,
27        unpredictable results occurred, instead of the error return
28        PCRE_ERROR_DFA_UITEM.
29    
30    5.  The C++ GlobalReplace function was not working like Perl for the special
31        situation when an empty string is matched. It now does the fancy magic
32        stuff that is necessary.
33    
34    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
35        removed. (These were left over from very, very early versions of PCRE.)
36    
37    7.  Some cosmetic changes to the code to make life easier when compiling it
38        as part of something else:
39    
40        (a) Change DEBUG to PCRE_DEBUG.
41    
42        (b) In pcre_compile(), rename the member of the "branch_chain" structure
43            called "current" as "current_branch", to prevent a collision with the
44            Linux macro when compiled as a kernel module.
45    
46        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
47            prevent a collision with the Linux macro when compiled as a kernel
48            module.
49    
50    8.  In pcre_compile() there are some checks for integer overflows that used to
51        cast potentially large values to (double). This has been changed to that
52        when building, a check for int64_t is made, and if it is found, it is used
53        instead, thus avoiding the use of floating point arithmetic. (There is no
54        other use of FP in PCRE.) If int64_t is not found, the fallback is to
55        double.
56    
57    
58    
59    Version 8.00 19-Oct-09
60    ----------------------
61    
62    1.  The table for translating pcre_compile() error codes into POSIX error codes
63        was out-of-date, and there was no check on the pcre_compile() error code
64        being within the table. This could lead to an OK return being given in
65        error.
66    
67    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
68        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
69        in a Windows environment.
70    
71    3.  The pcregrep --count option prints the count for each file even when it is
72        zero, as does GNU grep. However, pcregrep was also printing all files when
73        --files-with-matches was added. Now, when both options are given, it prints
74        counts only for those files that have at least one match. (GNU grep just
75        prints the file name in this circumstance, but including the count seems
76        more useful - otherwise, why use --count?) Also ensured that the
77        combination -clh just lists non-zero counts, with no names.
78    
79    4.  The long form of the pcregrep -F option was incorrectly implemented as
80        --fixed_strings instead of --fixed-strings. This is an incompatible change,
81        but it seems right to fix it, and I didn't think it was worth preserving
82        the old behaviour.
83    
84    5.  The command line items --regex=pattern and --regexp=pattern were not
85        recognized by pcregrep, which required --regex pattern or --regexp pattern
86        (with a space rather than an '='). The man page documented the '=' forms,
87        which are compatible with GNU grep; these now work.
88    
89    6.  No libpcreposix.pc file was created for pkg-config; there was just
90        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
91    
92    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
93        when UCP support is not needed, by modifying the Python script that
94        generates it from Unicode data files. This should not matter if the module
95        is correctly used as a library, but I received one complaint about 50K of
96        unwanted data. My guess is that the person linked everything into his
97        program rather than using a library. Anyway, it does no harm.
98    
99    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
100        was a minimum greater than 1 for a wide character in a possessive
101        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
102        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
103        character. Chaos in the form of incorrect output or a compiling loop could
104        result.
105    
106    9.  The restrictions on what a pattern can contain when partial matching is
107        requested for pcre_exec() have been removed. All patterns can now be
108        partially matched by this function. In addition, if there are at least two
109        slots in the offset vector, the offset of the earliest inspected character
110        for the match and the offset of the end of the subject are set in them when
111        PCRE_ERROR_PARTIAL is returned.
112    
113    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
114        synonymous with PCRE_PARTIAL, for backwards compatibility, and
115        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
116        and may be more useful for multi-segment matching.
117    
118    11. Partial matching with pcre_exec() is now more intuitive. A partial match
119        used to be given if ever the end of the subject was reached; now it is
120        given only if matching could not proceed because another character was
121        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
122        string "Z", which now yields "no match" instead of "partial match". In the
123        case of pcre_dfa_exec(), "no match" is given if every matching path for the
124        final character ended with (*FAIL).
125    
126    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
127        if the pattern had a "must contain" character that was already found in the
128        earlier partial match, unless partial matching was again requested. For
129        example, with the pattern /dog.(body)?/, the "must contain" character is
130        "g". If the first part-match was for the string "dog", restarting with
131        "sbody" failed. This bug has been fixed.
132    
133    13. The string returned by pcre_dfa_exec() after a partial match has been
134        changed so that it starts at the first inspected character rather than the
135        first character of the match. This makes a difference only if the pattern
136        starts with a lookbehind assertion or \b or \B (\K is not supported by
137        pcre_dfa_exec()). It's an incompatible change, but it makes the two
138        matching functions compatible, and I think it's the right thing to do.
139    
140    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
141        so that the demonstration program is easily available in environments where
142        PCRE has not been installed from source.
143    
144    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
145        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
146        library.
147    
148    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
149        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
150        is not the first non-POSIX option to be added. Clearly some people find
151        these options useful.
152    
153    17. If a caller to the POSIX matching function regexec() passes a non-zero
154        value for nmatch with a NULL value for pmatch, the value of
155        nmatch is forced to zero.
156    
157    18. RunGrepTest did not have a test for the availability of the -u option of
158        the diff command, as RunTest does. It now checks in the same way as
159        RunTest, and also checks for the -b option.
160    
161    19. If an odd number of negated classes containing just a single character
162        interposed, within parentheses, between a forward reference to a named
163        subpattern and the definition of the subpattern, compilation crashed with
164        an internal error, complaining that it could not find the referenced
165        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
166        [The bug was that it was starting one character too far in when skipping
167        over the character class, thus treating the ] as data rather than
168        terminating the class. This meant it could skip too much.]
169    
170    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
171        /g option in pcretest when the pattern contains \K, which makes it possible
172        to have an empty string match not at the start, even when the pattern is
173        anchored. Updated pcretest and pcredemo to use this option.
174    
175    21. If the maximum number of capturing subpatterns in a recursion was greater
176        than the maximum at the outer level, the higher number was returned, but
177        with unset values at the outer level. The correct (outer level) value is
178        now given.
179    
180    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
181        PCRE did not set those parentheses (unlike Perl). I have now found a way to
182        make it do so. The string so far is captured, making this feature
183        compatible with Perl.
184    
185    23. The tests have been re-organized, adding tests 11 and 12, to make it
186        possible to check the Perl 5.10 features against Perl 5.10.
187    
188    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
189        pattern matches a fixed length string. PCRE did not allow this; now it
190        does. Neither allows recursion.
191    
192    25. I finally figured out how to implement a request to provide the minimum
193        length of subject string that was needed in order to match a given pattern.
194        (It was back references and recursion that I had previously got hung up
195        on.) This code has now been added to pcre_study(); it finds a lower bound
196        to the length of subject needed. It is not necessarily the greatest lower
197        bound, but using it to avoid searching strings that are too short does give
198        some useful speed-ups. The value is available to calling programs via
199        pcre_fullinfo().
200    
201    26. While implementing 25, I discovered to my embarrassment that pcretest had
202        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
203        study optimizations had never been tested with that matching function.
204        Oops. What is worse, even when it was passed study data, there was a bug in
205        pcre_dfa_exec() that meant it never actually used it. Double oops. There
206        were also very few tests of studied patterns with pcre_dfa_exec().
207    
208    27. If (?| is used to create subpatterns with duplicate numbers, they are now
209        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
210        on the other side of the coin, they are no longer allowed to have different
211        names, because these cannot be distinguished in PCRE, and this has caused
212        confusion. (This is a difference from Perl.)
213    
214    28. When duplicate subpattern names are present (necessarily with different
215        numbers, as required by 27 above), and a test is made by name in a
216        conditional pattern, either for a subpattern having been matched, or for
217        recursion in such a pattern, all the associated numbered subpatterns are
218        tested, and the overall condition is true if the condition is true for any
219        one of them. This is the way Perl works, and is also more like the way
220        testing by number works.
221    
222    
223    Version 7.9 11-Apr-09
224    ---------------------
225    
226    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
227        (pcretest), all targets were linked against these libraries. This included
228        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
229        libraries. This caused unwanted dependencies to be created. This problem
230        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
231        pcretest is linked with readline.
232    
233    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
234        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
235        moved outside it again, because FALSE and TRUE are already defined in AIX,
236        but BOOL is not.
237    
238    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
239        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
240    
241    4.  The pcregrep documentation said spaces were inserted as well as colons (or
242        hyphens) following file names and line numbers when outputting matching
243        lines. This is not true; no spaces are inserted. I have also clarified the
244        wording for the --colour (or --color) option.
245    
246    5.  In pcregrep, when --colour was used with -o, the list of matching strings
247        was not coloured; this is different to GNU grep, so I have changed it to be
248        the same.
249    
250    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
251        each matching line was coloured. Now it goes on to look for further matches
252        of any of the test patterns, which is the same behaviour as GNU grep.
253    
254    7.  A pattern that could match an empty string could cause pcregrep to loop; it
255        doesn't make sense to accept an empty string match in pcregrep, so I have
256        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
257        seems to be how GNU grep behaves.
258    
259    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
260        start or after a newline", because the conditional assertion was not being
261        correctly handled. The rule now is that both the assertion and what follows
262        in the first alternative must satisfy the test.
263    
264    9.  If auto-callout was enabled in a pattern with a conditional group whose
265        condition was an assertion, PCRE could crash during matching, both with
266        pcre_exec() and pcre_dfa_exec().
267    
268    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
269        used for matching.
270    
271    11. Unicode property support in character classes was not working for
272        characters (bytes) greater than 127 when not in UTF-8 mode.
273    
274    12. Added the -M command line option to pcretest.
275    
276    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
277    
278    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
279    
280    16. Added comments and documentation about mis-use of no_arg in the C++
281        wrapper.
282    
283    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
284        from Martin Jerabek that uses macro names for all relevant character and
285        string constants.
286    
287    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
288        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
289        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
290        these, but not everybody uses configure.
291    
292    19. A conditional group that had only one branch was not being correctly
293        recognized as an item that could match an empty string. This meant that an
294        enclosing group might also not be so recognized, causing infinite looping
295        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
296        with the subject "ab", where knowledge that the repeated group can match
297        nothing is needed in order to break the loop.
298    
299    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
300        exec(), but without supplying a callout function, matching went wrong.
301    
302    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
303        leak if the size of the offset vector was greater than 30. When the vector
304        is smaller, the saved offsets during recursion go onto a local stack
305        vector, but for larger vectors malloc() is used. It was failing to free
306        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
307        error, in fact).
308    
309    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
310        heapframe that is used only when UTF-8 support is enabled. This caused no
311        problem, but was untidy.
312    
313    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
314        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
315        included within another project.
316    
317    24. Steven Van Ingelgem's patches to add more options to the CMake support,
318        slightly modified by me:
319    
320          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
321              not building pcregrep.
322    
323          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
324              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
325    
326    25. Forward references, both numeric and by name, in patterns that made use of
327        duplicate group numbers, could behave incorrectly or give incorrect errors,
328        because when scanning forward to find the reference group, PCRE was not
329        taking into account the duplicate group numbers. A pattern such as
330        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
331    
332    26. Changed a few more instances of "const unsigned char *" to USPTR, making
333        the feature of a custom pointer more persuasive (as requested by a user).
334    
335    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
336        pcretest.c, inside #ifndefs, because it seems they are sometimes already
337        pre-defined.
338    
339    28. Added support for (*UTF8) at the start of a pattern.
340    
341    29. Arrange for flags added by the "release type" setting in CMake to be shown
342        in the configuration summary.
343    
344    
345    Version 7.8 05-Sep-08
346    ---------------------
347    
348    1.  Replaced UCP searching code with optimized version as implemented for Ad
349        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
350        stage table and inline lookup instead of a function, giving speed ups of 2
351        to 5 times on some simple patterns that I tested. Permission was given to
352        distribute the MultiStage2.py script that generates the tables (it's not in
353        the tarball, but is in the Subversion repository).
354    
355    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
356        scripts.
357    
358    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
359        a group with a zero qualifier. The result of the study could be incorrect,
360        or the function might crash, depending on the pattern.
361    
362    4.  Caseless matching was not working for non-ASCII characters in back
363        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
364        It now works when Unicode Property Support is available.
365    
366    5.  In pcretest, an escape such as \x{de} in the data was always generating
367        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
368        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
369        truncation.
370    
371    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
372    
373    7.  Added two (int) casts to pcregrep when printing the difference of two
374        pointers, in case they are 64-bit values.
375    
376    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
377        test 2 if it fails.
378    
379    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
380        and a #define of that name to empty if it is not externally set. This is to
381        allow users of MSVC to set it if necessary.
382    
383    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
384        the convenience functions in the pcre_get.c source file.
385    
386    11. An option change at the start of a pattern that had top-level alternatives
387        could cause overwriting and/or a crash. This command provoked a crash in
388        some environments:
389    
390          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
391    
392        This potential security problem was recorded as CVE-2008-2371.
393    
394    12. For a pattern where the match had to start at the beginning or immediately
395        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
396        pcre_dfa_exec() could read past the end of the passed subject if there was
397        no match. To help with detecting such bugs (e.g. with valgrind), I modified
398        pcretest so that it places the subject at the end of its malloc-ed buffer.
399    
400    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
401        exec() might read past the end of the data buffer in UTF-8 mode.
402    
403    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
404        the data contained the byte 0x85 as part of a UTF-8 character within its
405        first line. This applied both to normal and DFA matching.
406    
407    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
408        /^[^d]*?$/8 failed to match "abc".
409    
410    16. Added a missing copyright notice to pcrecpp_internal.h.
411    
412    17. Make it more clear in the documentation that values returned from
413        pcre_exec() in ovector are byte offsets, not character counts.
414    
415    18. Tidied a few places to stop certain compilers from issuing warnings.
416    
417    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
418        supplied by Stefan Weber. I made a further small update for 7.8 because
419        there is a change of source arrangements: the pcre_searchfuncs.c module is
420        replaced by pcre_ucd.c.
421    
422    
423    Version 7.7 07-May-08
424    ---------------------
425    
426    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
427        a string to a long long, pretend we don't even have a long long." This is
428        done by checking for the strtoq, strtoll, and _strtoi64 functions.
429    
430    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
431        pre-7.6 versions, which defined a global no_arg variable instead of putting
432        it in the RE class. (See also #8 below.)
433    
434    3.  Remove a line of dead code, identified by coverity and reported by Nuno
435        Lopes.
436    
437    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
438    
439        (1) The include/exclude patterns were being applied to the whole pathnames
440            of files, instead of just to the final components.
441    
442        (2) If there was more than one level of directory, the subdirectories were
443            skipped unless they satisfied the include/exclude conditions. This is
444            inconsistent with GNU grep (and could even be seen as contrary to the
445            pcregrep specification - which I improved to make it absolutely clear).
446            The action now is always to scan all levels of directory, and just
447            apply the include/exclude patterns to regular files.
448    
449    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
450        --exclude_dir in the tests to avoid scanning .svn directories.
451    
452    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
453        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
454        doesn't support NULs in patterns.
455    
456    7.  Added some missing "const"s to declarations of static tables in
457        pcre_compile.c and pcre_dfa_exec.c.
458    
459    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
460        caused by fix #2  above. (Subsequently also a second patch to fix the
461        first patch. And a third patch - this was a messy problem.)
462    
463    9.  Applied Craig's patch to remove the use of push_back().
464    
465    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
466        matching function regexec().
467    
468    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
469        which, however, unlike Perl's \g{...}, are subroutine calls, not back
470        references. PCRE supports relative numbers with this syntax (I don't think
471        Oniguruma does).
472    
473    12. Previously, a group with a zero repeat such as (...){0} was completely
474        omitted from the compiled regex. However, this means that if the group
475        was called as a subroutine from elsewhere in the pattern, things went wrong
476        (an internal error was given). Such groups are now left in the compiled
477        pattern, with a new opcode that causes them to be skipped at execution
478        time.
479    
480    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
481        to the way PCRE behaves:
482    
483        (a) A lone ] character is dis-allowed (Perl treats it as data).
484    
485        (b) A back reference to an unmatched subpattern matches an empty string
486            (Perl fails the current match path).
487    
488        (c) A data ] in a character class must be notated as \] because if the
489            first data character in a class is ], it defines an empty class. (In
490            Perl it is not possible to have an empty class.) The empty class []
491            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
492            The negative empty class [^] matches any one character, independently
493            of the DOTALL setting.
494    
495    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
496        non-existent subpattern following a character class starting with ']' and
497        containing () gave an internal compiling error instead of "reference to
498        non-existent subpattern". Fortunately, when the pattern did exist, the
499        compiled code was correct. (When scanning forwards to check for the
500        existencd of the subpattern, it was treating the data ']' as terminating
501        the class, so got the count wrong. When actually compiling, the reference
502        was subsequently set up correctly.)
503    
504    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
505        it was being rejected as not supported by pcre_dfa_exec(), even though
506        other assertions are supported. I have made pcre_dfa_exec() support
507        (*FAIL).
508    
509    16. The implementation of 13c above involved the invention of a new opcode,
510        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
511        cannot be changed at match time, I realized I could make a small
512        improvement to matching performance by compiling OP_ALLANY instead of
513        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
514        on the OP_ANY path.
515    
516    17. Compiling pcretest on Windows with readline support failed without the
517        following two fixes: (1) Make the unistd.h include conditional on
518        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
519    
520    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
521        ncurses library to be included for pcretest when ReadLine support is
522        requested, but also to allow for it to be overridden. This patch came from
523        Daniel Bergström.
524    
525    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
526        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
527        any errors with the current Unicode tables. Thanks to Peter Kankowski for
528        spotting this.
529    
530    
531    Version 7.6 28-Jan-08
532    ---------------------
533    
534    1.  A character class containing a very large number of characters with
535        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
536        overflow.
537    
538    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
539        HAVE_LONG_LONG is not defined.
540    
541    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
542        bring them up to date and include new features. This patch includes:
543    
544        - Fixed PH's badly added libz and libbz2 support.
545        - Fixed a problem with static linking.
546        - Added pcredemo. [But later removed - see 7 below.]
547        - Fixed dftables problem and added an option.
548        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
549            HAVE_LONG_LONG.
550        - Added readline support for pcretest.
551        - Added an listing of the option settings after cmake has run.
552    
553    4.  A user submitted a patch to Makefile that makes it easy to create
554        "pcre.dll" under mingw when using Configure/Make. I added stuff to
555        Makefile.am that cause it to include this special target, without
556        affecting anything else. Note that the same mingw target plus all
557        the other distribution libraries and programs are now supported
558        when configuring with CMake (see 6 below) instead of with
559        Configure/Make.
560    
561    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
562        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
563        exported in the Windows port". It has not yet been confirmed that the patch
564        solves the problem, but it does no harm.
565    
566    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
567        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
568        with CMake, and also correct the comment about stack recursion.
569    
570    7.  Remove the automatic building of pcredemo from the ./configure system and
571        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
572        of a program that users should build themselves after PCRE is installed, so
573        building it automatically is not really right. What is more, it gave
574        trouble in some build environments.
575    
576    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
577    
578    
579    Version 7.5 10-Jan-08
580    ---------------------
581    
582    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
583        values in parens when parsing an RE using the C++ wrapper."
584    
585    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
586        Characters greater than 255 were excluded from the class instead of being
587        included.
588    
589    3.  The same bug as (2) above applied to negated POSIX classes such as
590        [:^space:].
591    
592    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
593        defined or documented. It seems to have been a typo for PCRE_STATIC, so
594        I have changed it.
595    
596    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
597        first named subpattern) and a construct such as (?&a) would reference the
598        first named subpattern whose name started with "a" (in other words, the
599        length check was missing). Both these problems are fixed. "Subpattern name
600        expected" is now given for (?&) (a zero-length name), and this patch also
601        makes it give the same error for \k'' (previously it complained that that
602        was a reference to a non-existent subpattern).
603    
604    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
605        this is right because (?- can be followed by option settings as well as by
606        digits. I have, however, made the messages clearer.
607    
608    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
609        than the number used in the conditional) now cause a compile-time error.
610        This is actually not compatible with Perl, which accepts such patterns, but
611        treats the conditional as always being FALSE (as PCRE used to), but it
612        seems to me that giving a diagnostic is better.
613    
614    8.  Change "alphameric" to the more common word "alphanumeric" in comments
615        and messages.
616    
617    9.  Fix two occurrences of "backslash" in comments that should have been
618        "backspace".
619    
620    10. Remove two redundant lines of code that can never be obeyed (their function
621        was moved elsewhere).
622    
623    11. The program that makes PCRE's Unicode character property table had a bug
624        which caused it to generate incorrect table entries for sequences of
625        characters that have the same character type, but are in different scripts.
626        It amalgamated them into a single range, with the script of the first of
627        them. In other words, some characters were in the wrong script. There were
628        thirteen such cases, affecting characters in the following ranges:
629    
630          U+002b0 - U+002c1
631          U+0060c - U+0060d
632          U+0061e - U+00612
633          U+0064b - U+0065e
634          U+0074d - U+0076d
635          U+01800 - U+01805
636          U+01d00 - U+01d77
637          U+01d9b - U+01dbf
638          U+0200b - U+0200f
639          U+030fc - U+030fe
640          U+03260 - U+0327f
641          U+0fb46 - U+0fbb1
642          U+10450 - U+1049d
643    
644    12. The -o option (show only the matching part of a line) for pcregrep was not
645        compatible with GNU grep in that, if there was more than one match in a
646        line, it showed only the first of them. It now behaves in the same way as
647        GNU grep.
648    
649    13. If the -o and -v options were combined for pcregrep, it printed a blank
650        line for every non-matching line. GNU grep prints nothing, and pcregrep now
651        does the same. The return code can be used to tell if there were any
652        non-matching lines.
653    
654    14. Added --file-offsets and --line-offsets to pcregrep.
655    
656    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
657        infinitely looping recursion. The bug was that positive lookaheads were not
658        being skipped when checking for a possible empty match (negative lookaheads
659        and both kinds of lookbehind were skipped).
660    
661    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
662        inclusion of <windows.h> to before rather than after the definition of
663        INVALID_FILE_ATTRIBUTES (patch from David Byron).
664    
665    17. Specifying a possessive quantifier with a specific limit for a Unicode
666        character property caused pcre_compile() to compile bad code, which led at
667        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
668        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
669        caused the error; without that there was no problem.
670    
671    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
672    
673    19. Added --enable-pcretest-libreadline.
674    
675    20. In pcrecpp.cc, the variable 'count' was incremented twice in
676        RE::GlobalReplace(). As a result, the number of replacements returned was
677        double what it should be. I removed one of the increments, but Craig sent a
678        later patch that removed the other one (the right fix) and added unit tests
679        that check the return values (which was not done before).
680    
681    21. Several CMake things:
682    
683        (1) Arranged that, when cmake is used on Unix, the libraries end up with
684            the names libpcre and libpcreposix, not just pcre and pcreposix.
685    
686        (2) The above change means that pcretest and pcregrep are now correctly
687            linked with the newly-built libraries, not previously installed ones.
688    
689        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
690    
691    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
692        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
693        UTF-8 newline character). The key issue is that the pattern starts .*;
694        this means that the match must be either at the beginning, or after a
695        newline. The bug was in the code for advancing after a failed match and
696        checking that the new position followed a newline. It was not taking
697        account of UTF-8 characters correctly.
698    
699    23. PCRE was behaving differently from Perl in the way it recognized POSIX
700        character classes. PCRE was not treating the sequence [:...:] as a
701        character class unless the ... were all letters. Perl, however, seems to
702        allow any characters between [: and :], though of course it rejects as
703        unknown any "names" that contain non-letters, because all the known class
704        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
705        for example, whereas PCRE did not - it did not recognize a POSIX character
706        class. This seemed a bit dangerous, so the code has been changed to be
707        closer to Perl. The behaviour is not identical to Perl, because PCRE will
708        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
709        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
710        Perl does, and where it didn't before.
711    
712    24. Rewrite so as to remove the single use of %n from pcregrep because in some
713        Windows environments %n is disabled by default.
714    
715    
716    Version 7.4 21-Sep-07
717    ---------------------
718    
719    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
720        means that a class such as [\s] counted as "explicit reference to CR or
721        LF". That isn't really right - the whole point of the change was to try to
722        help when there was an actual mention of one of the two characters. So now
723        the change happens only if \r or \n (or a literal CR or LF) character is
724        encountered.
725    
726    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
727        of both had grown to the point where there were only 3 bits left.
728        Fortunately, there was spare space in the data structure, and so I have
729        moved the internal flags into a new 16-bit field to free up more option
730        bits.
731    
732    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
733        but did not set the internal JCHANGED flag - either of these is enough to
734        control the way the "get" function works - but the PCRE_INFO_JCHANGED
735        facility is supposed to tell if (?J) was ever used, so now (?J) at the
736        start sets both bits.
737    
738    4.  Added options (at build time, compile time, exec time) to change \R from
739        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
740    
741    5.  doc/pcresyntax.html was missing from the distribution.
742    
743    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
744        compatibility, even though it is no longer used.
745    
746    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
747        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
748        windows.h file is present (where different names are used). [This was
749        reversed later after testing - see 16 below.]
750    
751    8.  Changed all #include <config.h> to #include "config.h". There were also
752        some further <pcre.h> cases that I changed to "pcre.h".
753    
754    9.  When pcregrep was used with the --colour option, it missed the line ending
755        sequence off the lines that it output.
756    
757    10. It was pointed out to me that arrays of string pointers cause lots of
758        relocations when a shared library is dynamically loaded. A technique of
759        using a single long string with a table of offsets can drastically reduce
760        these. I have refactored PCRE in four places to do this. The result is
761        dramatic:
762    
763          Originally:                          290
764          After changing UCP table:            187
765          After changing error message table:   43
766          After changing table of "verbs"       36
767          After changing table of Posix names   22
768    
769        Thanks to the folks working on Gregex for glib for this insight.
770    
771    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
772        unicode-properties was also set.
773    
774    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
775    
776    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
777        checked only for CRLF.
778    
779    14. Added casts to pcretest.c to avoid compiler warnings.
780    
781    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
782    
783    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
784        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
785        entirely. This removes changes made in 7 above.
786    
787    17. The CMake files have been updated, and there is now more information about
788        building with CMake in the NON-UNIX-USE document.
789    
790    
791    Version 7.3 28-Aug-07
792    ---------------------
793    
794     1. In the rejigging of the build system that eventually resulted in 7.1, the
795        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
796        brackets there is not right, since it causes compilers to look for an
797        installed pcre.h, not the version that is in the source that is being
798        compiled (which of course may be different). I have changed it back to:
799    
800          #include "pcre.h"
801    
802        I have a vague recollection that the change was concerned with compiling in
803        different directories, but in the new build system, that is taken care of
804        by the VPATH setting the Makefile.
805    
806     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
807        when the subject happened to end in the byte 0x85 (e.g. if the last
808        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
809        characters but of course it shouldn't be taken as a newline when it is part
810        of another character. The bug was that, for an unlimited repeat of . in
811        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
812        characters when looking for a newline.
813    
814     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
815    
816     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
817        in debug output.
818    
819     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
820        long printing in the pcrecpp unittest when running under MinGW.
821    
822     6. ESC_K was left out of the EBCDIC table.
823    
824     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
825        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
826        limit also applies to "virtual nesting" when a pattern is recursive, and in
827        this case 1000 isn't so big. I have been able to remove this limit at the
828        expense of backing off one optimization in certain circumstances. Normally,
829        when pcre_exec() would call its internal match() function recursively and
830        immediately return the result unconditionally, it uses a "tail recursion"
831        feature to save stack. However, when a subpattern that can match an empty
832        string has an unlimited repetition quantifier, it no longer makes this
833        optimization. That gives it a stack frame in which to save the data for
834        checking that an empty string has been matched. Previously this was taken
835        from the 1000-entry workspace that had been reserved. So now there is no
836        explicit limit, but more stack is used.
837    
838     8. Applied Daniel's patches to solve problems with the import/export magic
839        syntax that is required for Windows, and which was going wrong for the
840        pcreposix and pcrecpp parts of the library. These were overlooked when this
841        problem was solved for the main library.
842    
843     9. There were some crude static tests to avoid integer overflow when computing
844        the size of patterns that contain repeated groups with explicit upper
845        limits. As the maximum quantifier is 65535, the maximum group length was
846        set at 30,000 so that the product of these two numbers did not overflow a
847        32-bit integer. However, it turns out that people want to use groups that
848        are longer than 30,000 bytes (though not repeat them that many times).
849        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
850        made it possible to implement the integer overflow checks in a much more
851        dynamic way, which I have now done. The artificial limitation on group
852        length has been removed - we now have only the limit on the total length of
853        the compiled pattern, which depends on the LINK_SIZE setting.
854    
855    10. Fixed a bug in the documentation for get/copy named substring when
856        duplicate names are permitted. If none of the named substrings are set, the
857        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
858        empty string.
859    
860    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
861        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
862        because the ] is interpreted as the first data character and the
863        terminating ] is not found. PCRE has been made compatible with Perl in this
864        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
865        cause memory overwriting.
866    
867    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
868        string has been matched (to stop an infinite loop). It was not recognizing
869        a conditional subpattern that could match an empty string if that
870        subpattern was within another subpattern. For example, it looped when
871        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
872        condition was not nested. This bug has been fixed.
873    
874    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
875        past the start of the subject in the presence of bytes with the top bit
876        set, for example "\x8aBCD".
877    
878    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
879        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
880    
881    14. Optimized (?!) to (*FAIL).
882    
883    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
884        This restricts code points to be within the range 0 to 0x10FFFF, excluding
885        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
886        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
887        does: it's just the validity check that is more restrictive.
888    
889    16. Inserted checks for integer overflows during escape sequence (backslash)
890        processing, and also fixed erroneous offset values for syntax errors during
891        backslash processing.
892    
893    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
894        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
895    
896    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
897        caused an overrun.
898    
899    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
900        something other than just ASCII characters) inside a group that had an
901        unlimited repeat caused a loop at compile time (while checking to see
902        whether the group could match an empty string).
903    
904    20. Debugging a pattern containing \p or \P could cause a crash. For example,
905        [\P{Any}] did so. (Error in the code for printing property names.)
906    
907    21. An orphan \E inside a character class could cause a crash.
908    
909    22. A repeated capturing bracket such as (A)? could cause a wild memory
910        reference during compilation.
911    
912    23. There are several functions in pcre_compile() that scan along a compiled
913        expression for various reasons (e.g. to see if it's fixed length for look
914        behind). There were bugs in these functions when a repeated \p or \P was
915        present in the pattern. These operators have additional parameters compared
916        with \d, etc, and these were not being taken into account when moving along
917        the compiled data. Specifically:
918    
919        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
920            length.
921    
922        (b) An item such as \pL+ within a repeated group could cause crashes or
923            loops.
924    
925        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
926            "reference to non-existent subpattern" error.
927    
928        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
929    
930    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
931        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
932    
933    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
934    
935    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
936        character were causing crashes (broken optimization).
937    
938    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
939        \p or \P) caused a compile-time loop.
940    
941    28. More problems have arisen in unanchored patterns when CRLF is a valid line
942        break. For example, the unstudied pattern [\r\n]A does not match the string
943        "\r\nA" because change 7.0/46 below moves the current point on by two
944        characters after failing to match at the start. However, the pattern \nA
945        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
946        the same is true. There doesn't seem any very clean way out of this, but
947        what I have chosen to do makes the common cases work: PCRE now takes note
948        of whether there can be an explicit match for \r or \n anywhere in the
949        pattern, and if so, 7.0/46 no longer applies. As part of this change,
950        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
951        pattern has explicit CR or LF references.
952    
953    29. Added (*CR) etc for changing newline setting at start of pattern.
954    
955    
956    Version 7.2 19-Jun-07
957  ---------------------  ---------------------
958    
959   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 11  Version 7.2 01-May-07 Line 963  Version 7.2 01-May-07
963      to make them independent of the local environment's newline setting.      to make them independent of the local environment's newline setting.
964    
965   3. Add code to configure.ac to remove -g from the CFLAGS default settings.   3. Add code to configure.ac to remove -g from the CFLAGS default settings.
966    
967   4. Some of the "internals" tests were previously cut out when the link size   4. Some of the "internals" tests were previously cut out when the link size
968      was not 2, because the output contained actual offsets. The recent new      was not 2, because the output contained actual offsets. The recent new
969      "Z" feature of pcretest means that these can be cut out, making the tests      "Z" feature of pcretest means that these can be cut out, making the tests
970      usable with all link sizes.      usable with all link sizes.
971    
972     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
973        stack recursion. This gives a massive performance boost under BSD, but just
974        a small improvement under Linux. However, it saves one field in the frame
975        in all cases.
976    
977     6. Added more features from the forthcoming Perl 5.10:
978    
979        (a) (?-n) (where n is a string of digits) is a relative subroutine or
980            recursion call. It refers to the nth most recently opened parentheses.
981    
982        (b) (?+n) is also a relative subroutine call; it refers to the nth next
983            to be opened parentheses.
984    
985        (c) Conditions that refer to capturing parentheses can be specified
986            relatively, for example, (?(-2)... or (?(+3)...
987    
988        (d) \K resets the start of the current match so that everything before
989            is not part of it.
990    
991        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
992    
993        (f) \g{name} is another synonym - part of Perl 5.10's unification of
994            reference syntax.
995    
996        (g) (?| introduces a group in which the numbering of parentheses in each
997            alternative starts with the same number.
998    
999        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1000    
1001     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1002        PCRE_INFO_JCHANGED.
1003    
1004     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1005        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1006        for detecting groups that can match an empty string.
1007    
1008     9. A pattern with a very large number of alternatives (more than several
1009        hundred) was running out of internal workspace during the pre-compile
1010        phase, where pcre_compile() figures out how much memory will be needed. A
1011        bit of new cunning has reduced the workspace needed for groups with
1012        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1013        workspace instead of running out of the 4096 that are available.
1014    
1015    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1016    
1017    11. Applied patch from Google to remove an optimization that didn't quite work.
1018        The report of the bug said:
1019    
1020          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1021          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1022          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1023    
1024    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1025        it matched the wrong number of bytes.
1026    
1027    
1028  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

Legend:
Removed from v.161  
changed lines
  Added in v.475

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12