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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.218  
changed lines
  Added in v.471

  ViewVC Help
Powered by ViewVC 1.1.5