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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.69  
changed lines
  Added in v.378

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12