ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.205  
changed lines
  Added in v.426

  ViewVC Help
Powered by ViewVC 1.1.5