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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.172  
changed lines
  Added in v.421

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12