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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.228  
changed lines
  Added in v.429

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12