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

Diff of /code/trunk/ChangeLog

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

revision 267 by ph10, Wed Nov 14 11:48:49 2007 UTC revision 343 by ph10, Mon Apr 21 16:30:37 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 7.7 05-Mar-08
5    ---------------------
6    
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
10    
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class. (See also #8 below.)
14    
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
17    
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
19    
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
22    
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
29    
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
32    
33    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
34        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
35        doesn't support NULs in patterns.
36    
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
39    
40    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above. (Subsequently also a second patch to fix the
42        first patch. And a third patch - this was a messy problem.)
43    
44    9.  Applied Craig's patch to remove the use of push_back().
45    
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
48    
49    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
50        which, however, unlike Perl's \g{...}, are subroutine calls, not back
51        references. PCRE supports relative numbers with this syntax (I don't think
52        Oniguruma does).
53    
54    12. Previously, a group with a zero repeat such as (...){0} was completely
55        omitted from the compiled regex. However, this means that if the group
56        was called as a subroutine from elsewhere in the pattern, things went wrong
57        (an internal error was given). Such groups are now left in the compiled
58        pattern, with a new opcode that causes them to be skipped at execution
59        time.
60    
61    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
62        to the way PCRE behaves:
63    
64        (a) A lone ] character is dis-allowed (Perl treats it as data).
65    
66        (b) A back reference to an unmatched subpattern matches an empty string
67            (Perl fails the current match path).
68    
69        (c) A data ] in a character class must be notated as \] because if the
70            first data character in a class is ], it defines an empty class. (In
71            Perl it is not possible to have an empty class.) The empty class []
72            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
73            The negative empty class [^] matches any one character, independently
74            of the DOTALL setting.
75    
76    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
77        non-existent subpattern following a character class starting with ']' and
78        containing () gave an internal compiling error instead of "reference to
79        non-existent subpattern". Fortunately, when the pattern did exist, the
80        compiled code was correct. (When scanning forwards to check for the
81        existencd of the subpattern, it was treating the data ']' as terminating
82        the class, so got the count wrong. When actually compiling, the reference
83        was subsequently set up correctly.)
84    
85    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
86        it was being rejected as not supported by pcre_dfa_exec(), even though
87        other assertions are supported. I have made pcre_dfa_exec() support
88        (*FAIL).
89    
90    16. The implementation of 13c above involved the invention of a new opcode,
91        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
92        cannot be changed at match time, I realized I could make a small
93        improvement to matching performance by compiling OP_ALLANY instead of
94        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
95        on the OP_ANY path.
96    
97    17. Compiling pcretest on Windows with readline support failed without the
98        following two fixes: (1) Make the unistd.h include conditional on
99        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
100    
101    
102    Version 7.6 28-Jan-08
103    ---------------------
104    
105    1.  A character class containing a very large number of characters with
106        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
107        overflow.
108    
109    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
110        HAVE_LONG_LONG is not defined.
111    
112    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
113        bring them up to date and include new features. This patch includes:
114    
115        - Fixed PH's badly added libz and libbz2 support.
116        - Fixed a problem with static linking.
117        - Added pcredemo. [But later removed - see 7 below.]
118        - Fixed dftables problem and added an option.
119        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
120            HAVE_LONG_LONG.
121        - Added readline support for pcretest.
122        - Added an listing of the option settings after cmake has run.
123    
124    4.  A user submitted a patch to Makefile that makes it easy to create
125        "pcre.dll" under mingw when using Configure/Make. I added stuff to
126        Makefile.am that cause it to include this special target, without
127        affecting anything else. Note that the same mingw target plus all
128        the other distribution libraries and programs are now supported
129        when configuring with CMake (see 6 below) instead of with
130        Configure/Make.
131    
132    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
133        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
134        exported in the Windows port". It has not yet been confirmed that the patch
135        solves the problem, but it does no harm.
136    
137    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
138        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
139        with CMake, and also correct the comment about stack recursion.
140    
141    7.  Remove the automatic building of pcredemo from the ./configure system and
142        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
143        of a program that users should build themselves after PCRE is installed, so
144        building it automatically is not really right. What is more, it gave
145        trouble in some build environments.
146    
147    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
148    
149    
150    Version 7.5 10-Jan-08
151  ---------------------  ---------------------
152    
153  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
154      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
155    
156  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
157      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
158      included.      included.
159    
160  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
161      [:^space:].      [:^space:].
162    
163  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
164      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
165      I have changed it.      I have changed it.
166    
167    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
168        first named subpattern) and a construct such as (?&a) would reference the
169        first named subpattern whose name started with "a" (in other words, the
170        length check was missing). Both these problems are fixed. "Subpattern name
171        expected" is now given for (?&) (a zero-length name), and this patch also
172        makes it give the same error for \k'' (previously it complained that that
173        was a reference to a non-existent subpattern).
174    
175    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
176        this is right because (?- can be followed by option settings as well as by
177        digits. I have, however, made the messages clearer.
178    
179    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
180        than the number used in the conditional) now cause a compile-time error.
181        This is actually not compatible with Perl, which accepts such patterns, but
182        treats the conditional as always being FALSE (as PCRE used to), but it
183        seems to me that giving a diagnostic is better.
184    
185    8.  Change "alphameric" to the more common word "alphanumeric" in comments
186        and messages.
187    
188    9.  Fix two occurrences of "backslash" in comments that should have been
189        "backspace".
190    
191    10. Remove two redundant lines of code that can never be obeyed (their function
192        was moved elsewhere).
193    
194    11. The program that makes PCRE's Unicode character property table had a bug
195        which caused it to generate incorrect table entries for sequences of
196        characters that have the same character type, but are in different scripts.
197        It amalgamated them into a single range, with the script of the first of
198        them. In other words, some characters were in the wrong script. There were
199        thirteen such cases, affecting characters in the following ranges:
200    
201          U+002b0 - U+002c1
202          U+0060c - U+0060d
203          U+0061e - U+00612
204          U+0064b - U+0065e
205          U+0074d - U+0076d
206          U+01800 - U+01805
207          U+01d00 - U+01d77
208          U+01d9b - U+01dbf
209          U+0200b - U+0200f
210          U+030fc - U+030fe
211          U+03260 - U+0327f
212          U+0fb46 - U+0fbb1
213          U+10450 - U+1049d
214    
215    12. The -o option (show only the matching part of a line) for pcregrep was not
216        compatible with GNU grep in that, if there was more than one match in a
217        line, it showed only the first of them. It now behaves in the same way as
218        GNU grep.
219    
220    13. If the -o and -v options were combined for pcregrep, it printed a blank
221        line for every non-matching line. GNU grep prints nothing, and pcregrep now
222        does the same. The return code can be used to tell if there were any
223        non-matching lines.
224    
225    14. Added --file-offsets and --line-offsets to pcregrep.
226    
227    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
228        infinitely looping recursion. The bug was that positive lookaheads were not
229        being skipped when checking for a possible empty match (negative lookaheads
230        and both kinds of lookbehind were skipped).
231    
232    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
233        inclusion of <windows.h> to before rather than after the definition of
234        INVALID_FILE_ATTRIBUTES (patch from David Byron).
235    
236    17. Specifying a possessive quantifier with a specific limit for a Unicode
237        character property caused pcre_compile() to compile bad code, which led at
238        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
239        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
240        caused the error; without that there was no problem.
241    
242    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
243    
244    19. Added --enable-pcretest-libreadline.
245    
246    20. In pcrecpp.cc, the variable 'count' was incremented twice in
247        RE::GlobalReplace(). As a result, the number of replacements returned was
248        double what it should be. I removed one of the increments, but Craig sent a
249        later patch that removed the other one (the right fix) and added unit tests
250        that check the return values (which was not done before).
251    
252    21. Several CMake things:
253    
254        (1) Arranged that, when cmake is used on Unix, the libraries end up with
255            the names libpcre and libpcreposix, not just pcre and pcreposix.
256    
257        (2) The above change means that pcretest and pcregrep are now correctly
258            linked with the newly-built libraries, not previously installed ones.
259    
260        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
261    
262    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
263        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
264        UTF-8 newline character). The key issue is that the pattern starts .*;
265        this means that the match must be either at the beginning, or after a
266        newline. The bug was in the code for advancing after a failed match and
267        checking that the new position followed a newline. It was not taking
268        account of UTF-8 characters correctly.
269    
270    23. PCRE was behaving differently from Perl in the way it recognized POSIX
271        character classes. PCRE was not treating the sequence [:...:] as a
272        character class unless the ... were all letters. Perl, however, seems to
273        allow any characters between [: and :], though of course it rejects as
274        unknown any "names" that contain non-letters, because all the known class
275        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
276        for example, whereas PCRE did not - it did not recognize a POSIX character
277        class. This seemed a bit dangerous, so the code has been changed to be
278        closer to Perl. The behaviour is not identical to Perl, because PCRE will
279        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
280        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
281        Perl does, and where it didn't before.
282    
283    24. Rewrite so as to remove the single use of %n from pcregrep because in some
284        Windows environments %n is disabled by default.
285    
286    
287  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.267  
changed lines
  Added in v.343

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12