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

Diff of /code/trunk/ChangeLog

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

revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC revision 359 by ph10, Wed Jul 9 16:20:19 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 8.0 02 Jul-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
20    
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
24    
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    
46    Version 7.7 07-May-08
47    ---------------------
48    
49    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
50        a string to a long long, pretend we don't even have a long long." This is
51        done by checking for the strtoq, strtoll, and _strtoi64 functions.
52    
53    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
54        pre-7.6 versions, which defined a global no_arg variable instead of putting
55        it in the RE class. (See also #8 below.)
56    
57    3.  Remove a line of dead code, identified by coverity and reported by Nuno
58        Lopes.
59    
60    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
61    
62        (1) The include/exclude patterns were being applied to the whole pathnames
63            of files, instead of just to the final components.
64    
65        (2) If there was more than one level of directory, the subdirectories were
66            skipped unless they satisfied the include/exclude conditions. This is
67            inconsistent with GNU grep (and could even be seen as contrary to the
68            pcregrep specification - which I improved to make it absolutely clear).
69            The action now is always to scan all levels of directory, and just
70            apply the include/exclude patterns to regular files.
71    
72    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
73        --exclude_dir in the tests to avoid scanning .svn directories.
74    
75    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
76        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
77        doesn't support NULs in patterns.
78    
79    7.  Added some missing "const"s to declarations of static tables in
80        pcre_compile.c and pcre_dfa_exec.c.
81    
82    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
83        caused by fix #2  above. (Subsequently also a second patch to fix the
84        first patch. And a third patch - this was a messy problem.)
85    
86    9.  Applied Craig's patch to remove the use of push_back().
87    
88    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
89        matching function regexec().
90    
91    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
92        which, however, unlike Perl's \g{...}, are subroutine calls, not back
93        references. PCRE supports relative numbers with this syntax (I don't think
94        Oniguruma does).
95    
96    12. Previously, a group with a zero repeat such as (...){0} was completely
97        omitted from the compiled regex. However, this means that if the group
98        was called as a subroutine from elsewhere in the pattern, things went wrong
99        (an internal error was given). Such groups are now left in the compiled
100        pattern, with a new opcode that causes them to be skipped at execution
101        time.
102    
103    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
104        to the way PCRE behaves:
105    
106        (a) A lone ] character is dis-allowed (Perl treats it as data).
107    
108        (b) A back reference to an unmatched subpattern matches an empty string
109            (Perl fails the current match path).
110    
111        (c) A data ] in a character class must be notated as \] because if the
112            first data character in a class is ], it defines an empty class. (In
113            Perl it is not possible to have an empty class.) The empty class []
114            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
115            The negative empty class [^] matches any one character, independently
116            of the DOTALL setting.
117    
118    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
119        non-existent subpattern following a character class starting with ']' and
120        containing () gave an internal compiling error instead of "reference to
121        non-existent subpattern". Fortunately, when the pattern did exist, the
122        compiled code was correct. (When scanning forwards to check for the
123        existencd of the subpattern, it was treating the data ']' as terminating
124        the class, so got the count wrong. When actually compiling, the reference
125        was subsequently set up correctly.)
126    
127    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
128        it was being rejected as not supported by pcre_dfa_exec(), even though
129        other assertions are supported. I have made pcre_dfa_exec() support
130        (*FAIL).
131    
132    16. The implementation of 13c above involved the invention of a new opcode,
133        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
134        cannot be changed at match time, I realized I could make a small
135        improvement to matching performance by compiling OP_ALLANY instead of
136        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
137        on the OP_ANY path.
138    
139    17. Compiling pcretest on Windows with readline support failed without the
140        following two fixes: (1) Make the unistd.h include conditional on
141        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
142    
143    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
144        ncurses library to be included for pcretest when ReadLine support is
145        requested, but also to allow for it to be overridden. This patch came from
146        Daniel Bergström.
147    
148    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
149        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
150        any errors with the current Unicode tables. Thanks to Peter Kankowski for
151        spotting this.
152    
153    
154    Version 7.6 28-Jan-08
155    ---------------------
156    
157    1.  A character class containing a very large number of characters with
158        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
159        overflow.
160    
161    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
162        HAVE_LONG_LONG is not defined.
163    
164    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
165        bring them up to date and include new features. This patch includes:
166    
167        - Fixed PH's badly added libz and libbz2 support.
168        - Fixed a problem with static linking.
169        - Added pcredemo. [But later removed - see 7 below.]
170        - Fixed dftables problem and added an option.
171        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
172            HAVE_LONG_LONG.
173        - Added readline support for pcretest.
174        - Added an listing of the option settings after cmake has run.
175    
176    4.  A user submitted a patch to Makefile that makes it easy to create
177        "pcre.dll" under mingw when using Configure/Make. I added stuff to
178        Makefile.am that cause it to include this special target, without
179        affecting anything else. Note that the same mingw target plus all
180        the other distribution libraries and programs are now supported
181        when configuring with CMake (see 6 below) instead of with
182        Configure/Make.
183    
184    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
185        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
186        exported in the Windows port". It has not yet been confirmed that the patch
187        solves the problem, but it does no harm.
188    
189    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
190        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
191        with CMake, and also correct the comment about stack recursion.
192    
193    7.  Remove the automatic building of pcredemo from the ./configure system and
194        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
195        of a program that users should build themselves after PCRE is installed, so
196        building it automatically is not really right. What is more, it gave
197        trouble in some build environments.
198    
199    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
200    
201    
202    Version 7.5 10-Jan-08
203    ---------------------
204    
205    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
206        values in parens when parsing an RE using the C++ wrapper."
207    
208    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
209        Characters greater than 255 were excluded from the class instead of being
210        included.
211    
212    3.  The same bug as (2) above applied to negated POSIX classes such as
213        [:^space:].
214    
215    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
216        defined or documented. It seems to have been a typo for PCRE_STATIC, so
217        I have changed it.
218    
219    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
220        first named subpattern) and a construct such as (?&a) would reference the
221        first named subpattern whose name started with "a" (in other words, the
222        length check was missing). Both these problems are fixed. "Subpattern name
223        expected" is now given for (?&) (a zero-length name), and this patch also
224        makes it give the same error for \k'' (previously it complained that that
225        was a reference to a non-existent subpattern).
226    
227    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
228        this is right because (?- can be followed by option settings as well as by
229        digits. I have, however, made the messages clearer.
230    
231    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
232        than the number used in the conditional) now cause a compile-time error.
233        This is actually not compatible with Perl, which accepts such patterns, but
234        treats the conditional as always being FALSE (as PCRE used to), but it
235        seems to me that giving a diagnostic is better.
236    
237    8.  Change "alphameric" to the more common word "alphanumeric" in comments
238        and messages.
239    
240    9.  Fix two occurrences of "backslash" in comments that should have been
241        "backspace".
242    
243    10. Remove two redundant lines of code that can never be obeyed (their function
244        was moved elsewhere).
245    
246    11. The program that makes PCRE's Unicode character property table had a bug
247        which caused it to generate incorrect table entries for sequences of
248        characters that have the same character type, but are in different scripts.
249        It amalgamated them into a single range, with the script of the first of
250        them. In other words, some characters were in the wrong script. There were
251        thirteen such cases, affecting characters in the following ranges:
252    
253          U+002b0 - U+002c1
254          U+0060c - U+0060d
255          U+0061e - U+00612
256          U+0064b - U+0065e
257          U+0074d - U+0076d
258          U+01800 - U+01805
259          U+01d00 - U+01d77
260          U+01d9b - U+01dbf
261          U+0200b - U+0200f
262          U+030fc - U+030fe
263          U+03260 - U+0327f
264          U+0fb46 - U+0fbb1
265          U+10450 - U+1049d
266    
267    12. The -o option (show only the matching part of a line) for pcregrep was not
268        compatible with GNU grep in that, if there was more than one match in a
269        line, it showed only the first of them. It now behaves in the same way as
270        GNU grep.
271    
272    13. If the -o and -v options were combined for pcregrep, it printed a blank
273        line for every non-matching line. GNU grep prints nothing, and pcregrep now
274        does the same. The return code can be used to tell if there were any
275        non-matching lines.
276    
277    14. Added --file-offsets and --line-offsets to pcregrep.
278    
279    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
280        infinitely looping recursion. The bug was that positive lookaheads were not
281        being skipped when checking for a possible empty match (negative lookaheads
282        and both kinds of lookbehind were skipped).
283    
284    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
285        inclusion of <windows.h> to before rather than after the definition of
286        INVALID_FILE_ATTRIBUTES (patch from David Byron).
287    
288    17. Specifying a possessive quantifier with a specific limit for a Unicode
289        character property caused pcre_compile() to compile bad code, which led at
290        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
291        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
292        caused the error; without that there was no problem.
293    
294    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
295    
296    19. Added --enable-pcretest-libreadline.
297    
298    20. In pcrecpp.cc, the variable 'count' was incremented twice in
299        RE::GlobalReplace(). As a result, the number of replacements returned was
300        double what it should be. I removed one of the increments, but Craig sent a
301        later patch that removed the other one (the right fix) and added unit tests
302        that check the return values (which was not done before).
303    
304    21. Several CMake things:
305    
306        (1) Arranged that, when cmake is used on Unix, the libraries end up with
307            the names libpcre and libpcreposix, not just pcre and pcreposix.
308    
309        (2) The above change means that pcretest and pcregrep are now correctly
310            linked with the newly-built libraries, not previously installed ones.
311    
312        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
313    
314    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
315        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
316        UTF-8 newline character). The key issue is that the pattern starts .*;
317        this means that the match must be either at the beginning, or after a
318        newline. The bug was in the code for advancing after a failed match and
319        checking that the new position followed a newline. It was not taking
320        account of UTF-8 characters correctly.
321    
322    23. PCRE was behaving differently from Perl in the way it recognized POSIX
323        character classes. PCRE was not treating the sequence [:...:] as a
324        character class unless the ... were all letters. Perl, however, seems to
325        allow any characters between [: and :], though of course it rejects as
326        unknown any "names" that contain non-letters, because all the known class
327        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
328        for example, whereas PCRE did not - it did not recognize a POSIX character
329        class. This seemed a bit dangerous, so the code has been changed to be
330        closer to Perl. The behaviour is not identical to Perl, because PCRE will
331        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
332        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
333        Perl does, and where it didn't before.
334    
335    24. Rewrite so as to remove the single use of %n from pcregrep because in some
336        Windows environments %n is disabled by default.
337    
338    
339    Version 7.4 21-Sep-07
340    ---------------------
341    
342    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
343        means that a class such as [\s] counted as "explicit reference to CR or
344        LF". That isn't really right - the whole point of the change was to try to
345        help when there was an actual mention of one of the two characters. So now
346        the change happens only if \r or \n (or a literal CR or LF) character is
347        encountered.
348    
349    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
350        of both had grown to the point where there were only 3 bits left.
351        Fortunately, there was spare space in the data structure, and so I have
352        moved the internal flags into a new 16-bit field to free up more option
353        bits.
354    
355    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
356        but did not set the internal JCHANGED flag - either of these is enough to
357        control the way the "get" function works - but the PCRE_INFO_JCHANGED
358        facility is supposed to tell if (?J) was ever used, so now (?J) at the
359        start sets both bits.
360    
361    4.  Added options (at build time, compile time, exec time) to change \R from
362        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
363    
364    5.  doc/pcresyntax.html was missing from the distribution.
365    
366    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
367        compatibility, even though it is no longer used.
368    
369    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
370        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
371        windows.h file is present (where different names are used). [This was
372        reversed later after testing - see 16 below.]
373    
374    8.  Changed all #include <config.h> to #include "config.h". There were also
375        some further <pcre.h> cases that I changed to "pcre.h".
376    
377    9.  When pcregrep was used with the --colour option, it missed the line ending
378        sequence off the lines that it output.
379    
380    10. It was pointed out to me that arrays of string pointers cause lots of
381        relocations when a shared library is dynamically loaded. A technique of
382        using a single long string with a table of offsets can drastically reduce
383        these. I have refactored PCRE in four places to do this. The result is
384        dramatic:
385    
386          Originally:                          290
387          After changing UCP table:            187
388          After changing error message table:   43
389          After changing table of "verbs"       36
390          After changing table of Posix names   22
391    
392        Thanks to the folks working on Gregex for glib for this insight.
393    
394    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
395        unicode-properties was also set.
396    
397    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
398    
399    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
400        checked only for CRLF.
401    
402    14. Added casts to pcretest.c to avoid compiler warnings.
403    
404    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
405    
406    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
407        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
408        entirely. This removes changes made in 7 above.
409    
410    17. The CMake files have been updated, and there is now more information about
411        building with CMake in the NON-UNIX-USE document.
412    
413    
414    Version 7.3 28-Aug-07
415    ---------------------
416    
417     1. In the rejigging of the build system that eventually resulted in 7.1, the
418        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
419        brackets there is not right, since it causes compilers to look for an
420        installed pcre.h, not the version that is in the source that is being
421        compiled (which of course may be different). I have changed it back to:
422    
423          #include "pcre.h"
424    
425        I have a vague recollection that the change was concerned with compiling in
426        different directories, but in the new build system, that is taken care of
427        by the VPATH setting the Makefile.
428    
429     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
430        when the subject happened to end in the byte 0x85 (e.g. if the last
431        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
432        characters but of course it shouldn't be taken as a newline when it is part
433        of another character. The bug was that, for an unlimited repeat of . in
434        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
435        characters when looking for a newline.
436    
437     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
438    
439     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
440        in debug output.
441    
442     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
443        long printing in the pcrecpp unittest when running under MinGW.
444    
445     6. ESC_K was left out of the EBCDIC table.
446    
447     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
448        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
449        limit also applies to "virtual nesting" when a pattern is recursive, and in
450        this case 1000 isn't so big. I have been able to remove this limit at the
451        expense of backing off one optimization in certain circumstances. Normally,
452        when pcre_exec() would call its internal match() function recursively and
453        immediately return the result unconditionally, it uses a "tail recursion"
454        feature to save stack. However, when a subpattern that can match an empty
455        string has an unlimited repetition quantifier, it no longer makes this
456        optimization. That gives it a stack frame in which to save the data for
457        checking that an empty string has been matched. Previously this was taken
458        from the 1000-entry workspace that had been reserved. So now there is no
459        explicit limit, but more stack is used.
460    
461     8. Applied Daniel's patches to solve problems with the import/export magic
462        syntax that is required for Windows, and which was going wrong for the
463        pcreposix and pcrecpp parts of the library. These were overlooked when this
464        problem was solved for the main library.
465    
466     9. There were some crude static tests to avoid integer overflow when computing
467        the size of patterns that contain repeated groups with explicit upper
468        limits. As the maximum quantifier is 65535, the maximum group length was
469        set at 30,000 so that the product of these two numbers did not overflow a
470        32-bit integer. However, it turns out that people want to use groups that
471        are longer than 30,000 bytes (though not repeat them that many times).
472        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
473        made it possible to implement the integer overflow checks in a much more
474        dynamic way, which I have now done. The artificial limitation on group
475        length has been removed - we now have only the limit on the total length of
476        the compiled pattern, which depends on the LINK_SIZE setting.
477    
478    10. Fixed a bug in the documentation for get/copy named substring when
479        duplicate names are permitted. If none of the named substrings are set, the
480        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
481        empty string.
482    
483    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
484        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
485        because the ] is interpreted as the first data character and the
486        terminating ] is not found. PCRE has been made compatible with Perl in this
487        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
488        cause memory overwriting.
489    
490    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
491        string has been matched (to stop an infinite loop). It was not recognizing
492        a conditional subpattern that could match an empty string if that
493        subpattern was within another subpattern. For example, it looped when
494        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
495        condition was not nested. This bug has been fixed.
496    
497    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
498        past the start of the subject in the presence of bytes with the top bit
499        set, for example "\x8aBCD".
500    
501    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
502        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
503    
504    14. Optimized (?!) to (*FAIL).
505    
506    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
507        This restricts code points to be within the range 0 to 0x10FFFF, excluding
508        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
509        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
510        does: it's just the validity check that is more restrictive.
511    
512    16. Inserted checks for integer overflows during escape sequence (backslash)
513        processing, and also fixed erroneous offset values for syntax errors during
514        backslash processing.
515    
516    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
517        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
518    
519    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
520        caused an overrun.
521    
522    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
523        something other than just ASCII characters) inside a group that had an
524        unlimited repeat caused a loop at compile time (while checking to see
525        whether the group could match an empty string).
526    
527    20. Debugging a pattern containing \p or \P could cause a crash. For example,
528        [\P{Any}] did so. (Error in the code for printing property names.)
529    
530    21. An orphan \E inside a character class could cause a crash.
531    
532    22. A repeated capturing bracket such as (A)? could cause a wild memory
533        reference during compilation.
534    
535    23. There are several functions in pcre_compile() that scan along a compiled
536        expression for various reasons (e.g. to see if it's fixed length for look
537        behind). There were bugs in these functions when a repeated \p or \P was
538        present in the pattern. These operators have additional parameters compared
539        with \d, etc, and these were not being taken into account when moving along
540        the compiled data. Specifically:
541    
542        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
543            length.
544    
545        (b) An item such as \pL+ within a repeated group could cause crashes or
546            loops.
547    
548        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
549            "reference to non-existent subpattern" error.
550    
551        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
552    
553    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
554        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
555    
556    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
557    
558    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
559        character were causing crashes (broken optimization).
560    
561    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
562        \p or \P) caused a compile-time loop.
563    
564    28. More problems have arisen in unanchored patterns when CRLF is a valid line
565        break. For example, the unstudied pattern [\r\n]A does not match the string
566        "\r\nA" because change 7.0/46 below moves the current point on by two
567        characters after failing to match at the start. However, the pattern \nA
568        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
569        the same is true. There doesn't seem any very clean way out of this, but
570        what I have chosen to do makes the common cases work: PCRE now takes note
571        of whether there can be an explicit match for \r or \n anywhere in the
572        pattern, and if so, 7.0/46 no longer applies. As part of this change,
573        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
574        pattern has explicit CR or LF references.
575    
576    29. Added (*CR) etc for changing newline setting at start of pattern.
577    
578    
579    Version 7.2 19-Jun-07
580    ---------------------
581    
582     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
583        which is apparently normally available under Windows.
584    
585     2. Re-jig the pcregrep tests with different newline settings in an attempt
586        to make them independent of the local environment's newline setting.
587    
588     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
589    
590     4. Some of the "internals" tests were previously cut out when the link size
591        was not 2, because the output contained actual offsets. The recent new
592        "Z" feature of pcretest means that these can be cut out, making the tests
593        usable with all link sizes.
594    
595     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
596        stack recursion. This gives a massive performance boost under BSD, but just
597        a small improvement under Linux. However, it saves one field in the frame
598        in all cases.
599    
600     6. Added more features from the forthcoming Perl 5.10:
601    
602        (a) (?-n) (where n is a string of digits) is a relative subroutine or
603            recursion call. It refers to the nth most recently opened parentheses.
604    
605        (b) (?+n) is also a relative subroutine call; it refers to the nth next
606            to be opened parentheses.
607    
608        (c) Conditions that refer to capturing parentheses can be specified
609            relatively, for example, (?(-2)... or (?(+3)...
610    
611        (d) \K resets the start of the current match so that everything before
612            is not part of it.
613    
614        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
615    
616        (f) \g{name} is another synonym - part of Perl 5.10's unification of
617            reference syntax.
618    
619        (g) (?| introduces a group in which the numbering of parentheses in each
620            alternative starts with the same number.
621    
622        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
623    
624     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
625        PCRE_INFO_JCHANGED.
626    
627     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
628        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
629        for detecting groups that can match an empty string.
630    
631     9. A pattern with a very large number of alternatives (more than several
632        hundred) was running out of internal workspace during the pre-compile
633        phase, where pcre_compile() figures out how much memory will be needed. A
634        bit of new cunning has reduced the workspace needed for groups with
635        alternatives. The 1000-alternative test pattern now uses 12 bytes of
636        workspace instead of running out of the 4096 that are available.
637    
638    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
639    
640    11. Applied patch from Google to remove an optimization that didn't quite work.
641        The report of the bug said:
642    
643          pcrecpp::RE("a*").FullMatch("aaa") matches, while
644          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
645          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
646    
647    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
648        it matched the wrong number of bytes.
649    
650    
651    Version 7.1 24-Apr-07
652    ---------------------
653    
654     1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
655        that is more "standard", making use of automake and other Autotools. There
656        is some re-arrangement of the files and adjustment of comments consequent
657        on this.
658    
659     2. Part of the patch fixed a problem with the pcregrep tests. The test of -r
660        for recursive directory scanning broke on some systems because the files
661        are not scanned in any specific order and on different systems the order
662        was different. A call to "sort" has been inserted into RunGrepTest for the
663        approprate test as a short-term fix. In the longer term there may be an
664        alternative.
665    
666     3. I had an email from Eric Raymond about problems translating some of PCRE's
667        man pages to HTML (despite the fact that I distribute HTML pages, some
668        people do their own conversions for various reasons). The problems
669        concerned the use of low-level troff macros .br and .in. I have therefore
670        removed all such uses from the man pages (some were redundant, some could
671        be replaced by .nf/.fi pairs). The 132html script that I use to generate
672        HTML has been updated to handle .nf/.fi and to complain if it encounters
673        .br or .in.
674    
675     4. Updated comments in configure.ac that get placed in config.h.in and also
676        arranged for config.h to be included in the distribution, with the name
677        config.h.generic, for the benefit of those who have to compile without
678        Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
679    
680     5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
681        Weber: (1) pcre_internal.h was missing some function renames; (2) updated
682        makevp.bat for the current PCRE, using the additional files
683        makevp_c.txt, makevp_l.txt, and pcregexp.pas.
684    
685     6. A Windows user reported a minor discrepancy with test 2, which turned out
686        to be caused by a trailing space on an input line that had got lost in his
687        copy. The trailing space was an accident, so I've just removed it.
688    
689     7. Add -Wl,-R... flags in pcre-config.in for *BSD* systems, as I'm told
690        that is needed.
691    
692     8. Mark ucp_table (in ucptable.h) and ucp_gentype (in pcre_ucp_searchfuncs.c)
693        as "const" (a) because they are and (b) because it helps the PHP
694        maintainers who have recently made a script to detect big data structures
695        in the php code that should be moved to the .rodata section. I remembered
696        to update Builducptable as well, so it won't revert if ucptable.h is ever
697        re-created.
698    
699     9. Added some extra #ifdef SUPPORT_UTF8 conditionals into pcretest.c,
700        pcre_printint.src, pcre_compile.c, pcre_study.c, and pcre_tables.c, in
701        order to be able to cut out the UTF-8 tables in the latter when UTF-8
702        support is not required. This saves 1.5-2K of code, which is important in
703        some applications.
704    
705        Later: more #ifdefs are needed in pcre_ord2utf8.c and pcre_valid_utf8.c
706        so as not to refer to the tables, even though these functions will never be
707        called when UTF-8 support is disabled. Otherwise there are problems with a
708        shared library.
709    
710    10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
711    
712        (a) It was defining its arguments as char * instead of void *.
713    
714        (b) It was assuming that all moves were upwards in memory; this was true
715            a long time ago when I wrote it, but is no longer the case.
716    
717        The emulated memove() is provided for those environments that have neither
718        memmove() nor bcopy(). I didn't think anyone used it these days, but that
719        is clearly not the case, as these two bugs were recently reported.
720    
721    11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
722        and Detrail to create the HTML documentation, the .txt form of the man
723        pages, and it removes trailing spaces from listed files. It also creates
724        pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
725        case, it wraps all the #defines with #ifndefs. This script should be run
726        before "make dist".
727    
728    12. Fixed two fairly obscure bugs concerned with quantified caseless matching
729        with Unicode property support.
730    
731        (a) For a maximizing quantifier, if the two different cases of the
732            character were of different lengths in their UTF-8 codings (there are
733            some cases like this - I found 11), and the matching function had to
734            back up over a mixture of the two cases, it incorrectly assumed they
735            were both the same length.
736    
737        (b) When PCRE was configured to use the heap rather than the stack for
738            recursion during matching, it was not correctly preserving the data for
739            the other case of a UTF-8 character when checking ahead for a match
740            while processing a minimizing repeat. If the check also involved
741            matching a wide character, but failed, corruption could cause an
742            erroneous result when trying to check for a repeat of the original
743            character.
744    
745    13. Some tidying changes to the testing mechanism:
746    
747        (a) The RunTest script now detects the internal link size and whether there
748            is UTF-8 and UCP support by running ./pcretest -C instead of relying on
749            values substituted by "configure". (The RunGrepTest script already did
750            this for UTF-8.) The configure.ac script no longer substitutes the
751            relevant variables.
752    
753        (b) The debugging options /B and /D in pcretest show the compiled bytecode
754            with length and offset values. This means that the output is different
755            for different internal link sizes. Test 2 is skipped for link sizes
756            other than 2 because of this, bypassing the problem. Unfortunately,
757            there was also a test in test 3 (the locale tests) that used /B and
758            failed for link sizes other than 2. Rather than cut the whole test out,
759            I have added a new /Z option to pcretest that replaces the length and
760            offset values with spaces. This is now used to make test 3 independent
761            of link size. (Test 2 will be tidied up later.)
762    
763    14. If erroroffset was passed as NULL to pcre_compile, it provoked a
764        segmentation fault instead of returning the appropriate error message.
765    
766    15. In multiline mode when the newline sequence was set to "any", the pattern
767        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
768        This doesn't seem right; it now treats the CRLF combination as the line
769        ending, and so does not match in that case. It's only a pattern such as ^$
770        that would hit this one: something like ^ABC$ would have failed after \r
771        and then tried again after \r\n.
772    
773    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
774        in an attempt to make files that differ only in their line terminators
775        compare equal. This works on Linux.
776    
777    17. Under certain error circumstances pcregrep might try to free random memory
778        as it exited. This is now fixed, thanks to valgrind.
779    
780    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
781        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
782        was because its rules for how to advance for /g after matching an empty
783        string at the end of a line did not allow for this case. They now check for
784        it specially.
785    
786    20. pcretest is supposed to handle patterns and data of any length, by
787        extending its buffers when necessary. It was getting this wrong when the
788        buffer for a data line had to be extended.
789    
790    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
791        CRLF as a newline sequence.
792    
793    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
794        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
795        I have nevertheless tidied it up.
796    
797    23. Added some casts to kill warnings from HP-UX ia64 compiler.
798    
799    24. Added a man page for pcre-config.
800    
801    
802    Version 7.0 19-Dec-06
803    ---------------------
804    
805     1. Fixed a signed/unsigned compiler warning in pcre_compile.c, shown up by
806        moving to gcc 4.1.1.
807    
808     2. The -S option for pcretest uses setrlimit(); I had omitted to #include
809        sys/time.h, which is documented as needed for this function. It doesn't
810        seem to matter on Linux, but it showed up on some releases of OS X.
811    
812     3. It seems that there are systems where bytes whose values are greater than
813        127 match isprint() in the "C" locale. The "C" locale should be the
814        default when a C program starts up. In most systems, only ASCII printing
815        characters match isprint(). This difference caused the output from pcretest
816        to vary, making some of the tests fail. I have changed pcretest so that:
817    
818        (a) When it is outputting text in the compiled version of a pattern, bytes
819            other than 32-126 are always shown as hex escapes.
820    
821        (b) When it is outputting text that is a matched part of a subject string,
822            it does the same, unless a different locale has been set for the match
823            (using the /L modifier). In this case, it uses isprint() to decide.
824    
825     4. Fixed a major bug that caused incorrect computation of the amount of memory
826        required for a compiled pattern when options that changed within the
827        pattern affected the logic of the preliminary scan that determines the
828        length. The relevant options are -x, and -i in UTF-8 mode. The result was
829        that the computed length was too small. The symptoms of this bug were
830        either the PCRE error "internal error: code overflow" from pcre_compile(),
831        or a glibc crash with a message such as "pcretest: free(): invalid next
832        size (fast)". Examples of patterns that provoked this bug (shown in
833        pcretest format) are:
834    
835          /(?-x: )/x
836          /(?x)(?-x: \s*#\s*)/
837          /((?i)[\x{c0}])/8
838          /(?i:[\x{c0}])/8
839    
840        HOWEVER: Change 17 below makes this fix obsolete as the memory computation
841        is now done differently.
842    
843     5. Applied patches from Google to: (a) add a QuoteMeta function to the C++
844        wrapper classes; (b) implement a new function in the C++ scanner that is
845        more efficient than the old way of doing things because it avoids levels of
846        recursion in the regex matching; (c) add a paragraph to the documentation
847        for the FullMatch() function.
848    
849     6. The escape sequence \n was being treated as whatever was defined as
850        "newline". Not only was this contrary to the documentation, which states
851        that \n is character 10 (hex 0A), but it also went horribly wrong when
852        "newline" was defined as CRLF. This has been fixed.
853    
854     7. In pcre_dfa_exec.c the value of an unsigned integer (the variable called c)
855        was being set to -1 for the "end of line" case (supposedly a value that no
856        character can have). Though this value is never used (the check for end of
857        line is "zero bytes in current character"), it caused compiler complaints.
858        I've changed it to 0xffffffff.
859    
860     8. In pcre_version.c, the version string was being built by a sequence of
861        C macros that, in the event of PCRE_PRERELEASE being defined as an empty
862        string (as it is for production releases) called a macro with an empty
863        argument. The C standard says the result of this is undefined. The gcc
864        compiler treats it as an empty string (which was what was wanted) but it is
865        reported that Visual C gives an error. The source has been hacked around to
866        avoid this problem.
867    
868     9. On the advice of a Windows user, included <io.h> and <fcntl.h> in Windows
869        builds of pcretest, and changed the call to _setmode() to use _O_BINARY
870        instead of 0x8000. Made all the #ifdefs test both _WIN32 and WIN32 (not all
871        of them did).
872    
873    10. Originally, pcretest opened its input and output without "b"; then I was
874        told that "b" was needed in some environments, so it was added for release
875        5.0 to both the input and output. (It makes no difference on Unix-like
876        systems.) Later I was told that it is wrong for the input on Windows. I've
877        now abstracted the modes into two macros, to make it easier to fiddle with
878        them, and removed "b" from the input mode under Windows.
879    
880    11. Added pkgconfig support for the C++ wrapper library, libpcrecpp.
881    
882    12. Added -help and --help to pcretest as an official way of being reminded
883        of the options.
884    
885    13. Removed some redundant semicolons after macro calls in pcrecpparg.h.in
886        and pcrecpp.cc because they annoy compilers at high warning levels.
887    
888    14. A bit of tidying/refactoring in pcre_exec.c in the main bumpalong loop.
889    
890    15. Fixed an occurrence of == in configure.ac that should have been = (shell
891        scripts are not C programs :-) and which was not noticed because it works
892        on Linux.
893    
894    16. pcretest is supposed to handle any length of pattern and data line (as one
895        line or as a continued sequence of lines) by extending its input buffer if
896        necessary. This feature was broken for very long pattern lines, leading to
897        a string of junk being passed to pcre_compile() if the pattern was longer
898        than about 50K.
899    
900    17. I have done a major re-factoring of the way pcre_compile() computes the
901        amount of memory needed for a compiled pattern. Previously, there was code
902        that made a preliminary scan of the pattern in order to do this. That was
903        OK when PCRE was new, but as the facilities have expanded, it has become
904        harder and harder to keep it in step with the real compile phase, and there
905        have been a number of bugs (see for example, 4 above). I have now found a
906        cunning way of running the real compile function in a "fake" mode that
907        enables it to compute how much memory it would need, while actually only
908        ever using a few hundred bytes of working memory and without too many
909        tests of the mode. This should make future maintenance and development
910        easier. A side effect of this work is that the limit of 200 on the nesting
911        depth of parentheses has been removed (though this was never a serious
912        limitation, I suspect). However, there is a downside: pcre_compile() now
913        runs more slowly than before (30% or more, depending on the pattern). I
914        hope this isn't a big issue. There is no effect on runtime performance.
915    
916    18. Fixed a minor bug in pcretest: if a pattern line was not terminated by a
917        newline (only possible for the last line of a file) and it was a
918        pattern that set a locale (followed by /Lsomething), pcretest crashed.
919    
920    19. Added additional timing features to pcretest. (1) The -tm option now times
921        matching only, not compiling. (2) Both -t and -tm can be followed, as a
922        separate command line item, by a number that specifies the number of
923        repeats to use when timing. The default is 50000; this gives better
924        precision, but takes uncomfortably long for very large patterns.
925    
926    20. Extended pcre_study() to be more clever in cases where a branch of a
927        subpattern has no definite first character. For example, (a*|b*)[cd] would
928        previously give no result from pcre_study(). Now it recognizes that the
929        first character must be a, b, c, or d.
930    
931    21. There was an incorrect error "recursive call could loop indefinitely" if
932        a subpattern (or the entire pattern) that was being tested for matching an
933        empty string contained only one non-empty item after a nested subpattern.
934        For example, the pattern (?>\x{100}*)\d(?R) provoked this error
935        incorrectly, because the \d was being skipped in the check.
936    
937    22. The pcretest program now has a new pattern option /B and a command line
938        option -b, which is equivalent to adding /B to every pattern. This causes
939        it to show the compiled bytecode, without the additional information that
940        -d shows. The effect of -d is now the same as -b with -i (and similarly, /D
941        is the same as /B/I).
942    
943    23. A new optimization is now able automatically to treat some sequences such
944        as a*b as a*+b. More specifically, if something simple (such as a character
945        or a simple class like \d) has an unlimited quantifier, and is followed by
946        something that cannot possibly match the quantified thing, the quantifier
947        is automatically "possessified".
948    
949    24. A recursive reference to a subpattern whose number was greater than 39
950        went wrong under certain circumstances in UTF-8 mode. This bug could also
951        have affected the operation of pcre_study().
952    
953    25. Realized that a little bit of performance could be had by replacing
954        (c & 0xc0) == 0xc0 with c >= 0xc0 when processing UTF-8 characters.
955    
956    26. Timing data from pcretest is now shown to 4 decimal places instead of 3.
957    
958    27. Possessive quantifiers such as a++ were previously implemented by turning
959        them into atomic groups such as ($>a+). Now they have their own opcodes,
960        which improves performance. This includes the automatically created ones
961        from 23 above.
962    
963    28. A pattern such as (?=(\w+))\1: which simulates an atomic group using a
964        lookahead was broken if it was not anchored. PCRE was mistakenly expecting
965        the first matched character to be a colon. This applied both to named and
966        numbered groups.
967    
968    29. The ucpinternal.h header file was missing its idempotency #ifdef.
969    
970    30. I was sent a "project" file called libpcre.a.dev which I understand makes
971        building PCRE on Windows easier, so I have included it in the distribution.
972    
973    31. There is now a check in pcretest against a ridiculously large number being
974        returned by pcre_exec() or pcre_dfa_exec(). If this happens in a /g or /G
975        loop, the loop is abandoned.
976    
977    32. Forward references to subpatterns in conditions such as (?(2)...) where
978        subpattern 2 is defined later cause pcre_compile() to search forwards in
979        the pattern for the relevant set of parentheses. This search went wrong
980        when there were unescaped parentheses in a character class, parentheses
981        escaped with \Q...\E, or parentheses in a #-comment in /x mode.
982    
983    33. "Subroutine" calls and backreferences were previously restricted to
984        referencing subpatterns earlier in the regex. This restriction has now
985        been removed.
986    
987    34. Added a number of extra features that are going to be in Perl 5.10. On the
988        whole, these are just syntactic alternatives for features that PCRE had
989        previously implemented using the Python syntax or my own invention. The
990        other formats are all retained for compatibility.
991    
992        (a) Named groups can now be defined as (?<name>...) or (?'name'...) as well
993            as (?P<name>...). The new forms, as well as being in Perl 5.10, are
994            also .NET compatible.
995    
996        (b) A recursion or subroutine call to a named group can now be defined as
997            (?&name) as well as (?P>name).
998    
999        (c) A backreference to a named group can now be defined as \k<name> or
1000            \k'name' as well as (?P=name). The new forms, as well as being in Perl
1001            5.10, are also .NET compatible.
1002    
1003        (d) A conditional reference to a named group can now use the syntax
1004            (?(<name>) or (?('name') as well as (?(name).
1005    
1006        (e) A "conditional group" of the form (?(DEFINE)...) can be used to define
1007            groups (named and numbered) that are never evaluated inline, but can be
1008            called as "subroutines" from elsewhere. In effect, the DEFINE condition
1009            is always false. There may be only one alternative in such a group.
1010    
1011        (f) A test for recursion can be given as (?(R1).. or (?(R&name)... as well
1012            as the simple (?(R). The condition is true only if the most recent
1013            recursion is that of the given number or name. It does not search out
1014            through the entire recursion stack.
1015    
1016        (g) The escape \gN or \g{N} has been added, where N is a positive or
1017            negative number, specifying an absolute or relative reference.
1018    
1019    35. Tidied to get rid of some further signed/unsigned compiler warnings and
1020        some "unreachable code" warnings.
1021    
1022    36. Updated the Unicode property tables to Unicode version 5.0.0. Amongst other
1023        things, this adds five new scripts.
1024    
1025    37. Perl ignores orphaned \E escapes completely. PCRE now does the same.
1026        There were also incompatibilities regarding the handling of \Q..\E inside
1027        character classes, for example with patterns like [\Qa\E-\Qz\E] where the
1028        hyphen was adjacent to \Q or \E. I hope I've cleared all this up now.
1029    
1030    38. Like Perl, PCRE detects when an indefinitely repeated parenthesized group
1031        matches an empty string, and forcibly breaks the loop. There were bugs in
1032        this code in non-simple cases. For a pattern such as  ^(a()*)*  matched
1033        against  aaaa  the result was just "a" rather than "aaaa", for example. Two
1034        separate and independent bugs (that affected different cases) have been
1035        fixed.
1036    
1037    39. Refactored the code to abolish the use of different opcodes for small
1038        capturing bracket numbers. This is a tidy that I avoided doing when I
1039        removed the limit on the number of capturing brackets for 3.5 back in 2001.
1040        The new approach is not only tidier, it makes it possible to reduce the
1041        memory needed to fix the previous bug (38).
1042    
1043    40. Implemented PCRE_NEWLINE_ANY to recognize any of the Unicode newline
1044        sequences (http://unicode.org/unicode/reports/tr18/) as "newline" when
1045        processing dot, circumflex, or dollar metacharacters, or #-comments in /x
1046        mode.
1047    
1048    41. Add \R to match any Unicode newline sequence, as suggested in the Unicode
1049        report.
1050    
1051    42. Applied patch, originally from Ari Pollak, modified by Google, to allow
1052        copy construction and assignment in the C++ wrapper.
1053    
1054    43. Updated pcregrep to support "--newline=any". In the process, I fixed a
1055        couple of bugs that could have given wrong results in the "--newline=crlf"
1056        case.
1057    
1058    44. Added a number of casts and did some reorganization of signed/unsigned int
1059        variables following suggestions from Dair Grant. Also renamed the variable
1060        "this" as "item" because it is a C++ keyword.
1061    
1062    45. Arranged for dftables to add
1063    
1064          #include "pcre_internal.h"
1065    
1066        to pcre_chartables.c because without it, gcc 4.x may remove the array
1067        definition from the final binary if PCRE is built into a static library and
1068        dead code stripping is activated.
1069    
1070    46. For an unanchored pattern, if a match attempt fails at the start of a
1071        newline sequence, and the newline setting is CRLF or ANY, and the next two
1072        characters are CRLF, advance by two characters instead of one.
1073    
1074    
1075    Version 6.7 04-Jul-06
1076    ---------------------
1077    
1078     1. In order to handle tests when input lines are enormously long, pcretest has
1079        been re-factored so that it automatically extends its buffers when
1080        necessary. The code is crude, but this _is_ just a test program. The
1081        default size has been increased from 32K to 50K.
1082    
1083     2. The code in pcre_study() was using the value of the re argument before
1084        testing it for NULL. (Of course, in any sensible call of the function, it
1085        won't be NULL.)
1086    
1087     3. The memmove() emulation function in pcre_internal.h, which is used on
1088        systems that lack both memmove() and bcopy() - that is, hardly ever -
1089        was missing a "static" storage class specifier.
1090    
1091     4. When UTF-8 mode was not set, PCRE looped when compiling certain patterns
1092        containing an extended class (one that cannot be represented by a bitmap
1093        because it contains high-valued characters or Unicode property items, e.g.
1094        [\pZ]). Almost always one would set UTF-8 mode when processing such a
1095        pattern, but PCRE should not loop if you do not (it no longer does).
1096        [Detail: two cases were found: (a) a repeated subpattern containing an
1097        extended class; (b) a recursive reference to a subpattern that followed a
1098        previous extended class. It wasn't skipping over the extended class
1099        correctly when UTF-8 mode was not set.]
1100    
1101     5. A negated single-character class was not being recognized as fixed-length
1102        in lookbehind assertions such as (?<=[^f]), leading to an incorrect
1103        compile error "lookbehind assertion is not fixed length".
1104    
1105     6. The RunPerlTest auxiliary script was showing an unexpected difference
1106        between PCRE and Perl for UTF-8 tests. It turns out that it is hard to
1107        write a Perl script that can interpret lines of an input file either as
1108        byte characters or as UTF-8, which is what "perltest" was being required to
1109        do for the non-UTF-8 and UTF-8 tests, respectively. Essentially what you
1110        can't do is switch easily at run time between having the "use utf8;" pragma
1111        or not. In the end, I fudged it by using the RunPerlTest script to insert
1112        "use utf8;" explicitly for the UTF-8 tests.
1113    
1114     7. In multiline (/m) mode, PCRE was matching ^ after a terminating newline at
1115        the end of the subject string, contrary to the documentation and to what
1116        Perl does. This was true of both matching functions. Now it matches only at
1117        the start of the subject and immediately after *internal* newlines.
1118    
1119     8. A call of pcre_fullinfo() from pcretest to get the option bits was passing
1120        a pointer to an int instead of a pointer to an unsigned long int. This
1121        caused problems on 64-bit systems.
1122    
1123     9. Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
1124        instance of the 'standard' template library not being so standard".
1125    
1126    10. There was no check on the number of named subpatterns nor the maximum
1127        length of a subpattern name. The product of these values is used to compute
1128        the size of the memory block for a compiled pattern. By supplying a very
1129        long subpattern name and a large number of named subpatterns, the size
1130        computation could be caused to overflow. This is now prevented by limiting
1131        the length of names to 32 characters, and the number of named subpatterns
1132        to 10,000.
1133    
1134    11. Subpatterns that are repeated with specific counts have to be replicated in
1135        the compiled pattern. The size of memory for this was computed from the
1136        length of the subpattern and the repeat count. The latter is limited to
1137        65535, but there was no limit on the former, meaning that integer overflow
1138        could in principle occur. The compiled length of a repeated subpattern is
1139        now limited to 30,000 bytes in order to prevent this.
1140    
1141    12. Added the optional facility to have named substrings with the same name.
1142    
1143    13. Added the ability to use a named substring as a condition, using the
1144        Python syntax: (?(name)yes|no). This overloads (?(R)... and names that
1145        are numbers (not recommended). Forward references are permitted.
1146    
1147    14. Added forward references in named backreferences (if you see what I mean).
1148    
1149    15. In UTF-8 mode, with the PCRE_DOTALL option set, a quantified dot in the
1150        pattern could run off the end of the subject. For example, the pattern
1151        "(?s)(.{1,5})"8 did this with the subject "ab".
1152    
1153    16. If PCRE_DOTALL or PCRE_MULTILINE were set, pcre_dfa_exec() behaved as if
1154        PCRE_CASELESS was set when matching characters that were quantified with ?
1155        or *.
1156    
1157    17. A character class other than a single negated character that had a minimum
1158        but no maximum quantifier - for example [ab]{6,} - was not handled
1159        correctly by pce_dfa_exec(). It would match only one character.
1160    
1161    18. A valid (though odd) pattern that looked like a POSIX character
1162        class but used an invalid character after [ (for example [[,abc,]]) caused
1163        pcre_compile() to give the error "Failed: internal error: code overflow" or
1164        in some cases to crash with a glibc free() error. This could even happen if
1165        the pattern terminated after [[ but there just happened to be a sequence of
1166        letters, a binary zero, and a closing ] in the memory that followed.
1167    
1168    19. Perl's treatment of octal escapes in the range \400 to \777 has changed
1169        over the years. Originally (before any Unicode support), just the bottom 8
1170        bits were taken. Thus, for example, \500 really meant \100. Nowadays the
1171        output from "man perlunicode" includes this:
1172    
1173          The regular expression compiler produces polymorphic opcodes.  That
1174          is, the pattern adapts to the data and automatically switches to
1175          the Unicode character scheme when presented with Unicode data--or
1176          instead uses a traditional byte scheme when presented with byte
1177          data.
1178    
1179        Sadly, a wide octal escape does not cause a switch, and in a string with
1180        no other multibyte characters, these octal escapes are treated as before.
1181        Thus, in Perl, the pattern  /\500/ actually matches \100 but the pattern
1182        /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
1183        Unicode string.
1184    
1185        I have not perpetrated such confusion in PCRE. Up till now, it took just
1186        the bottom 8 bits, as in old Perl. I have now made octal escapes with
1187        values greater than \377 illegal in non-UTF-8 mode. In UTF-8 mode they
1188        translate to the appropriate multibyte character.
1189    
1190    29. Applied some refactoring to reduce the number of warnings from Microsoft
1191        and Borland compilers. This has included removing the fudge introduced
1192        seven years ago for the OS/2 compiler (see 2.02/2 below) because it caused
1193        a warning about an unused variable.
1194    
1195    21. PCRE has not included VT (character 0x0b) in the set of whitespace
1196        characters since release 4.0, because Perl (from release 5.004) does not.
1197        [Or at least, is documented not to: some releases seem to be in conflict
1198        with the documentation.] However, when a pattern was studied with
1199        pcre_study() and all its branches started with \s, PCRE still included VT
1200        as a possible starting character. Of course, this did no harm; it just
1201        caused an unnecessary match attempt.
1202    
1203    22. Removed a now-redundant internal flag bit that recorded the fact that case
1204        dependency changed within the pattern. This was once needed for "required
1205        byte" processing, but is no longer used. This recovers a now-scarce options
1206        bit. Also moved the least significant internal flag bit to the most-
1207        significant bit of the word, which was not previously used (hangover from
1208        the days when it was an int rather than a uint) to free up another bit for
1209        the future.
1210    
1211    23. Added support for CRLF line endings as well as CR and LF. As well as the
1212        default being selectable at build time, it can now be changed at runtime
1213        via the PCRE_NEWLINE_xxx flags. There are now options for pcregrep to
1214        specify that it is scanning data with non-default line endings.
1215    
1216    24. Changed the definition of CXXLINK to make it agree with the definition of
1217        LINK in the Makefile, by replacing LDFLAGS to CXXFLAGS.
1218    
1219    25. Applied Ian Taylor's patches to avoid using another stack frame for tail
1220        recursions. This makes a big different to stack usage for some patterns.
1221    
1222    26. If a subpattern containing a named recursion or subroutine reference such
1223        as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
1224        the space required for the compiled pattern went wrong and gave too small a
1225        value. Depending on the environment, this could lead to "Failed: internal
1226        error: code overflow at offset 49" or "glibc detected double free or
1227        corruption" errors.
1228    
1229    27. Applied patches from Google (a) to support the new newline modes and (b) to
1230        advance over multibyte UTF-8 characters in GlobalReplace.
1231    
1232    28. Change free() to pcre_free() in pcredemo.c. Apparently this makes a
1233        difference for some implementation of PCRE in some Windows version.
1234    
1235    29. Added some extra testing facilities to pcretest:
1236    
1237        \q<number>   in a data line sets the "match limit" value
1238        \Q<number>   in a data line sets the "match recursion limt" value
1239        -S <number>  sets the stack size, where <number> is in megabytes
1240    
1241        The -S option isn't available for Windows.
1242    
1243    
1244    Version 6.6 06-Feb-06
1245    ---------------------
1246    
1247     1. Change 16(a) for 6.5 broke things, because PCRE_DATA_SCOPE was not defined
1248        in pcreposix.h. I have copied the definition from pcre.h.
1249    
1250     2. Change 25 for 6.5 broke compilation in a build directory out-of-tree
1251        because pcre.h is no longer a built file.
1252    
1253     3. Added Jeff Friedl's additional debugging patches to pcregrep. These are
1254        not normally included in the compiled code.
1255    
1256    
1257    Version 6.5 01-Feb-06
1258    ---------------------
1259    
1260     1. When using the partial match feature with pcre_dfa_exec(), it was not
1261        anchoring the second and subsequent partial matches at the new starting
1262        point. This could lead to incorrect results. For example, with the pattern
1263        /1234/, partially matching against "123" and then "a4" gave a match.
1264    
1265     2. Changes to pcregrep:
1266    
1267        (a) All non-match returns from pcre_exec() were being treated as failures
1268            to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an
1269            error message is output. Some extra information is given for the
1270            PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are
1271            probably the only errors that are likely to be caused by users (by
1272            specifying a regex that has nested indefinite repeats, for instance).
1273            If there are more than 20 of these errors, pcregrep is abandoned.
1274    
1275        (b) A binary zero was treated as data while matching, but terminated the
1276            output line if it was written out. This has been fixed: binary zeroes
1277            are now no different to any other data bytes.
1278    
1279        (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is
1280            used to set a locale for matching. The --locale=xxxx long option has
1281            been added (no short equivalent) to specify a locale explicitly on the
1282            pcregrep command, overriding the environment variables.
1283    
1284        (d) When -B was used with -n, some line numbers in the output were one less
1285            than they should have been.
1286    
1287        (e) Added the -o (--only-matching) option.
1288    
1289        (f) If -A or -C was used with -c (count only), some lines of context were
1290            accidentally printed for the final match.
1291    
1292        (g) Added the -H (--with-filename) option.
1293    
1294        (h) The combination of options -rh failed to suppress file names for files
1295            that were found from directory arguments.
1296    
1297        (i) Added the -D (--devices) and -d (--directories) options.
1298    
1299        (j) Added the -F (--fixed-strings) option.
1300    
1301        (k) Allow "-" to be used as a file name for -f as well as for a data file.
1302    
1303        (l) Added the --colo(u)r option.
1304    
1305        (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it
1306            is not present by default.
1307    
1308     3. A nasty bug was discovered in the handling of recursive patterns, that is,
1309        items such as (?R) or (?1), when the recursion could match a number of
1310        alternatives. If it matched one of the alternatives, but subsequently,
1311        outside the recursion, there was a failure, the code tried to back up into
1312        the recursion. However, because of the way PCRE is implemented, this is not
1313        possible, and the result was an incorrect result from the match.
1314    
1315        In order to prevent this happening, the specification of recursion has
1316        been changed so that all such subpatterns are automatically treated as
1317        atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)).
1318    
1319     4. I had overlooked the fact that, in some locales, there are characters for
1320        which isalpha() is true but neither isupper() nor islower() are true. In
1321        the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine
1322        and ordfeminine) are like this. This affected the treatment of \w and \W
1323        when they appeared in character classes, but not when they appeared outside
1324        a character class. The bit map for "word" characters is now created
1325        separately from the results of isalnum() instead of just taking it from the
1326        upper, lower, and digit maps. (Plus the underscore character, of course.)
1327    
1328     5. The above bug also affected the handling of POSIX character classes such as
1329        [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's
1330        permanent tables. Instead, the bit maps for such a class were previously
1331        created as the appropriate unions of the upper, lower, and digit bitmaps.
1332        Now they are created by subtraction from the [[:word:]] class, which has
1333        its own bitmap.
1334    
1335     6. The [[:blank:]] character class matches horizontal, but not vertical space.
1336        It is created by subtracting the vertical space characters (\x09, \x0a,
1337        \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the
1338        subtraction was done in the overall bitmap for a character class, meaning
1339        that a class such as [\x0c[:blank:]] was incorrect because \x0c would not
1340        be recognized. This bug has been fixed.
1341    
1342     7. Patches from the folks at Google:
1343    
1344          (a) pcrecpp.cc: "to handle a corner case that may or may not happen in
1345          real life, but is still worth protecting against".
1346    
1347          (b) pcrecpp.cc: "corrects a bug when negative radixes are used with
1348          regular expressions".
1349    
1350          (c) pcre_scanner.cc: avoid use of std::count() because not all systems
1351          have it.
1352    
1353          (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by
1354          "configure" and the latter not, in order to fix a problem somebody had
1355          with compiling the Arg class on HP-UX.
1356    
1357          (e) Improve the error-handling of the C++ wrapper a little bit.
1358    
1359          (f) New tests for checking recursion limiting.
1360    
1361     8. The pcre_memmove() function, which is used only if the environment does not
1362        have a standard memmove() function (and is therefore rarely compiled),
1363        contained two bugs: (a) use of int instead of size_t, and (b) it was not
1364        returning a result (though PCRE never actually uses the result).
1365    
1366     9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously
1367        large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is
1368        returned instead of calling malloc() with an overflowing number that would
1369        most likely cause subsequent chaos.
1370    
1371    10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag.
1372    
1373    11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled
1374        with this option is matched, the nmatch and pmatch options of regexec() are
1375        ignored.
1376    
1377    12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is
1378        provided in case anyone wants to the the POSIX interface with UTF-8
1379        strings.
1380    
1381    13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the
1382        C++ linking (needed for some HP-UX environments).
1383    
1384    14. Avoid compiler warnings in get_ucpname() when compiled without UCP support
1385        (unused parameter) and in the pcre_printint() function (omitted "default"
1386        switch label when the default is to do nothing).
1387    
1388    15. Added some code to make it possible, when PCRE is compiled as a C++
1389        library, to replace subject pointers for pcre_exec() with a smart pointer
1390        class, thus making it possible to process discontinuous strings.
1391    
1392    16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform
1393        much the same function. They were added by different people who were trying
1394        to make PCRE easy to compile on non-Unix systems. It has been suggested
1395        that PCRE_EXPORT be abolished now that there is more automatic apparatus
1396        for compiling on Windows systems. I have therefore replaced it with
1397        PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it
1398        defaults to "extern" for C or "extern C" for C++, which works fine on
1399        Unix-like systems. It is now possible to override the value of PCRE_DATA_
1400        SCOPE with something explicit in config.h. In addition:
1401    
1402        (a) pcreposix.h still had just "extern" instead of either of these macros;
1403            I have replaced it with PCRE_DATA_SCOPE.
1404    
1405        (b) Functions such as _pcre_xclass(), which are internal to the library,
1406            but external in the C sense, all had PCRE_EXPORT in their definitions.
1407            This is apparently wrong for the Windows case, so I have removed it.
1408            (It makes no difference on Unix-like systems.)
1409    
1410    17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting
1411        of recursive calls to match(). This is different to MATCH_LIMIT because
1412        that limits the total number of calls to match(), not all of which increase
1413        the depth of recursion. Limiting the recursion depth limits the amount of
1414        stack (or heap if NO_RECURSE is set) that is used. The default can be set
1415        when PCRE is compiled, and changed at run time. A patch from Google adds
1416        this functionality to the C++ interface.
1417    
1418    18. Changes to the handling of Unicode character properties:
1419    
1420        (a) Updated the table to Unicode 4.1.0.
1421    
1422        (b) Recognize characters that are not in the table as "Cn" (undefined).
1423    
1424        (c) I revised the way the table is implemented to a much improved format
1425            which includes recognition of ranges. It now supports the ranges that
1426            are defined in UnicodeData.txt, and it also amalgamates other
1427            characters into ranges. This has reduced the number of entries in the
1428            table from around 16,000 to around 3,000, thus reducing its size
1429            considerably. I realized I did not need to use a tree structure after
1430            all - a binary chop search is just as efficient. Having reduced the
1431            number of entries, I extended their size from 6 bytes to 8 bytes to
1432            allow for more data.
1433    
1434        (d) Added support for Unicode script names via properties such as \p{Han}.
1435    
1436    19. In UTF-8 mode, a backslash followed by a non-Ascii character was not
1437        matching that character.
1438    
1439    20. When matching a repeated Unicode property with a minimum greater than zero,
1440        (for example \pL{2,}), PCRE could look past the end of the subject if it
1441        reached it while seeking the minimum number of characters. This could
1442        happen only if some of the characters were more than one byte long, because
1443        there is a check for at least the minimum number of bytes.
1444    
1445    21. Refactored the implementation of \p and \P so as to be more general, to
1446        allow for more different types of property in future. This has changed the
1447        compiled form incompatibly. Anybody with saved compiled patterns that use
1448        \p or \P will have to recompile them.
1449    
1450    22. Added "Any" and "L&" to the supported property types.
1451    
1452    23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
1453        but give a compile time error if the value is greater than 0xff.
1454    
1455    24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were
1456        accidentally not being installed or uninstalled.
1457    
1458    25. The pcre.h file was built from pcre.h.in, but the only changes that were
1459        made were to insert the current release number. This seemed silly, because
1460        it made things harder for people building PCRE on systems that don't run
1461        "configure". I have turned pcre.h into a distributed file, no longer built
1462        by "configure", with the version identification directly included. There is
1463        no longer a pcre.h.in file.
1464    
1465        However, this change necessitated a change to the pcre-config script as
1466        well. It is built from pcre-config.in, and one of the substitutions was the
1467        release number. I have updated configure.ac so that ./configure now finds
1468        the release number by grepping pcre.h.
1469    
1470    26. Added the ability to run the tests under valgrind.
1471    
1472    
1473    Version 6.4 05-Sep-05
1474    ---------------------
1475    
1476     1. Change 6.0/10/(l) to pcregrep introduced a bug that caused separator lines
1477        "--" to be printed when multiple files were scanned, even when none of the
1478        -A, -B, or -C options were used. This is not compatible with Gnu grep, so I
1479        consider it to be a bug, and have restored the previous behaviour.
1480    
1481     2. A couple of code tidies to get rid of compiler warnings.
1482    
1483     3. The pcretest program used to cheat by referring to symbols in the library
1484        whose names begin with _pcre_. These are internal symbols that are not
1485        really supposed to be visible externally, and in some environments it is
1486        possible to suppress them. The cheating is now confined to including
1487        certain files from the library's source, which is a bit cleaner.
1488    
1489     4. Renamed pcre.in as pcre.h.in to go with pcrecpp.h.in; it also makes the
1490        file's purpose clearer.
1491    
1492     5. Reorganized pcre_ucp_findchar().
1493    
1494    
1495  Version 6.3 15-Aug-05  Version 6.3 15-Aug-05
1496  ---------------------  ---------------------
1497    

Legend:
Removed from v.83  
changed lines
  Added in v.359

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12