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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.73  
changed lines
  Added in v.289

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12