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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.195  
changed lines
  Added in v.423

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12