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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.158  
changed lines
  Added in v.437

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12