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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.203  
changed lines
  Added in v.418

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12