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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.208  
changed lines
  Added in v.454

  ViewVC Help
Powered by ViewVC 1.1.5