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

Diff of /code/trunk/ChangeLog

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

revision 51 by nigel, Sat Feb 24 21:39:37 2007 UTC revision 79 by nigel, Sat Feb 24 21:40:52 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    Version 6.1 21-Jun-05
5    ---------------------
6    
7     1. There was one reference to the variable "posix" in pcretest.c that was not
8        surrounded by "#if !defined NOPOSIX".
9    
10     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
11        the cross-check on the old pcre_info() function, for the benefit of the
12        cut-down version of PCRE that is currently imported into Exim.
13    
14     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
15        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
16        patterns that start (?i) but I don't think that matters. The use of (?i) is
17        just an example; this all applies to the other options as well.
18    
19     4. Since libtool seems to echo the compile commands it is issuing, the output
20        from "make" can be reduced a bit by putting "@" in front of each libtool
21        compile command.
22    
23     5. Patch from the folks at Google for configure.in to be a bit more thorough
24        in checking for a suitable C++ installation before trying to compile the
25        C++ stuff. This should fix a reported problem when a compiler was present,
26        but no suitable headers.
27    
28     6. The man pages all had just "PCRE" as their title. I have changed them to
29        be the relevant file name. I have also arranged that these names are
30        retained in the file doc/pcre.txt, which is a concatenation in text format
31        of all the man pages except the little individual ones for each function.
32    
33     7. The NON-UNIX-USE file had not been updated for the different set of source
34        files that come with release 6. I also added a few comments about the C++
35        wrapper.
36    
37    
38    Version 6.0 07-Jun-05
39    ---------------------
40    
41     1. Some minor internal re-organization to help with my DFA experiments.
42    
43     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
44        didn't matter for the library itself when fully configured, but did matter
45        when compiling without UCP support, or within Exim, where the ucp files are
46        not imported.
47    
48     3. Refactoring of the library code to split up the various functions into
49        different source modules. The addition of the new DFA matching code (see
50        below) to a single monolithic source would have made it really too
51        unwieldy, quite apart from causing all the code to be include in a
52        statically linked application, when only some functions are used. This is
53        relevant even without the DFA addition now that patterns can be compiled in
54        one application and matched in another.
55    
56        The downside of splitting up is that there have to be some external
57        functions and data tables that are used internally in different modules of
58        the library but which are not part of the API. These have all had their
59        names changed to start with "_pcre_" so that they are unlikely to clash
60        with other external names.
61    
62     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
63        a different (DFA) algorithm. Although it is slower than the original
64        function, it does have some advantages for certain types of matching
65        problem.
66    
67     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
68        including restarting after a partial match.
69    
70     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
71        defined when compiling for Windows was sent to me. I have put it into the
72        code, though I have no means of testing or verifying it.
73    
74     7. Added the pcre_refcount() auxiliary function.
75    
76     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
77        match before or at the first newline in the subject string. In pcretest,
78        the /f option on a pattern can be used to set this.
79    
80     9. A repeated \w when used in UTF-8 mode with characters greater than 256
81        would behave wrongly. This has been present in PCRE since release 4.0.
82    
83    10. A number of changes to the pcregrep command:
84    
85        (a) Refactored how -x works; insert ^(...)$ instead of setting
86            PCRE_ANCHORED and checking the length, in preparation for adding
87            something similar for -w.
88    
89        (b) Added the -w (match as a word) option.
90    
91        (c) Refactored the way lines are read and buffered so as to have more
92            than one at a time available.
93    
94        (d) Implemented a pcregrep test script.
95    
96        (e) Added the -M (multiline match) option. This allows patterns to match
97            over several lines of the subject. The buffering ensures that at least
98            8K, or the rest of the document (whichever is the shorter) is available
99            for matching (and similarly the previous 8K for lookbehind assertions).
100    
101        (f) Changed the --help output so that it now says
102    
103              -w, --word-regex(p)
104    
105            instead of two lines, one with "regex" and the other with "regexp"
106            because that confused at least one person since the short forms are the
107            same. (This required a bit of code, as the output is generated
108            automatically from a table. It wasn't just a text change.)
109    
110        (g) -- can be used to terminate pcregrep options if the next thing isn't an
111            option but starts with a hyphen. Could be a pattern or a path name
112            starting with a hyphen, for instance.
113    
114        (h) "-" can be given as a file name to represent stdin.
115    
116        (i) When file names are being printed, "(standard input)" is used for
117            the standard input, for compatibility with GNU grep. Previously
118            "<stdin>" was used.
119    
120        (j) The option --label=xxx can be used to supply a name to be used for
121            stdin when file names are being printed. There is no short form.
122    
123        (k) Re-factored the options decoding logic because we are going to add
124            two more options that take data. Such options can now be given in four
125            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
126    
127        (l) Added the -A, -B, and -C options for requesting that lines of context
128            around matches be printed.
129    
130        (m) Added the -L option to print the names of files that do not contain
131            any matching lines, that is, the complement of -l.
132    
133        (n) The return code is 2 if any file cannot be opened, but pcregrep does
134            continue to scan other files.
135    
136        (o) The -s option was incorrectly implemented. For compatibility with other
137            greps, it now suppresses the error message for a non-existent or non-
138            accessible file (but not the return code). There is a new option called
139            -q that suppresses the output of matching lines, which was what -s was
140            previously doing.
141    
142        (p) Added --include and --exclude options to specify files for inclusion
143            and exclusion when recursing.
144    
145    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
146        Hopefully, it now does.
147    
148    12. Missing cast in pcre_study().
149    
150    13. Added an "uninstall" target to the makefile.
151    
152    14. Replaced "extern" in the function prototypes in Makefile.in with
153        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
154        world, but is set differently for Windows.
155    
156    15. Added a second compiling function called pcre_compile2(). The only
157        difference is that it has an extra argument, which is a pointer to an
158        integer error code. When there is a compile-time failure, this is set
159        non-zero, in addition to the error test pointer being set to point to an
160        error message. The new argument may be NULL if no error number is required
161        (but then you may as well call pcre_compile(), which is now just a
162        wrapper). This facility is provided because some applications need a
163        numeric error indication, but it has also enabled me to tidy up the way
164        compile-time errors are handled in the POSIX wrapper.
165    
166    16. Added VPATH=.libs to the makefile; this should help when building with one
167        prefix path and installing with another. (Or so I'm told by someone who
168        knows more about this stuff than I do.)
169    
170    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
171        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
172        match everything, including newlines. This is not POSIX-compatible, but
173        somebody wanted the feature. From pcretest it can be activated by using
174        both the P and the s flags.
175    
176    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
177    
178    19. libpcre.pc was being incorrectly installed as executable.
179    
180    20. A couple of places in pcretest check for end-of-line by looking for '\n';
181        it now also looks for '\r' so that it will work unmodified on Windows.
182    
183    21. Added Google's contributed C++ wrapper to the distribution.
184    
185    22. Added some untidy missing memory free() calls in pcretest, to keep
186        Electric Fence happy when testing.
187    
188    
189    
190    Version 5.0 13-Sep-04
191    ---------------------
192    
193     1. Internal change: literal characters are no longer packed up into items
194        containing multiple characters in a single byte-string. Each character
195        is now matched using a separate opcode. However, there may be more than one
196        byte in the character in UTF-8 mode.
197    
198     2. The pcre_callout_block structure has two new fields: pattern_position and
199        next_item_length. These contain the offset in the pattern to the next match
200        item, and its length, respectively.
201    
202     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
203        insertion of callouts before each pattern item. Added the /C option to
204        pcretest to make use of this.
205    
206     4. On the advice of a Windows user, the lines
207    
208          #if defined(_WIN32) || defined(WIN32)
209          _setmode( _fileno( stdout ), 0x8000 );
210          #endif  /* defined(_WIN32) || defined(WIN32) */
211    
212        have been added to the source of pcretest. This apparently does useful
213        magic in relation to line terminators.
214    
215     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
216        for the benefit of those environments where the "b" makes a difference.
217    
218     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
219        to know about it. I have put a hack into configure.in that adds in code
220        to set GCC=yes if CC=icc. This seems to end up at a point in the
221        generated configure script that is early enough to affect the setting of
222        compiler options, which is what is needed, but I have no means of testing
223        whether it really works. (The user who reported this had patched the
224        generated configure script, which of course I cannot do.)
225    
226        LATER: After change 22 below (new libtool files), the configure script
227        seems to know about icc (and also ecc). Therefore, I have commented out
228        this hack in configure.in.
229    
230     7. Added support for pkg-config (2 patches were sent in).
231    
232     8. Negated POSIX character classes that used a combination of internal tables
233        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
234        [[:^ascii]]. Typically, they would match almost any characters. The other
235        POSIX classes were not broken in this way.
236    
237     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
238        to find the match, as PCRE was deluded into thinking that the match had to
239        start at the start point or following a newline. The same bug applied to
240        patterns with negative forward assertions or any backward assertions
241        preceding ".*" at the start, unless the pattern required a fixed first
242        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
243    
244    10. In UTF-8 mode, when moving forwards in the subject after a failed match
245        starting at the last subject character, bytes beyond the end of the subject
246        string were read.
247    
248    11. Renamed the variable "class" as "classbits" to make life easier for C++
249        users. (Previously there was a macro definition, but it apparently wasn't
250        enough.)
251    
252    12. Added the new field "tables" to the extra data so that tables can be passed
253        in at exec time, or the internal tables can be re-selected. This allows
254        a compiled regex to be saved and re-used at a later time by a different
255        program that might have everything at different addresses.
256    
257    13. Modified the pcre-config script so that, when run on Solaris, it shows a
258        -R library as well as a -L library.
259    
260    14. The debugging options of pcretest (-d on the command line or D on a
261        pattern) showed incorrect output for anything following an extended class
262        that contained multibyte characters and which was followed by a quantifier.
263    
264    15. Added optional support for general category Unicode character properties
265        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
266        support. It adds about 90K to the size of the library. The meanings of the
267        inbuilt class escapes such as \d and \s have NOT been changed.
268    
269    16. Updated pcredemo.c to include calls to free() to release the memory for the
270        compiled pattern.
271    
272    17. The generated file chartables.c was being created in the source directory
273        instead of in the building directory. This caused the build to fail if the
274        source directory was different from the building directory, and was
275        read-only.
276    
277    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
278        file. No doubt somebody will tell me if they don't make sense... Also added
279        Dan Mooney's comments about building on OpenVMS.
280    
281    19. Added support for partial matching via the PCRE_PARTIAL option for
282        pcre_exec() and the \P data escape in pcretest.
283    
284    20. Extended pcretest with 3 new pattern features:
285    
286        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
287              write the compiled pattern to the file whose name is "rest-of-line".
288              This is a straight binary dump of the data, with the saved pointer to
289              the character tables forced to be NULL. The study data, if any, is
290              written too. After writing, pcretest reads a new pattern.
291    
292        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
293              compiled pattern from the given file. There must not be any
294              occurrences of "<" in the file name (pretty unlikely); if there are,
295              pcretest will instead treat the initial "<" as a pattern delimiter.
296              After reading in the pattern, pcretest goes on to read data lines as
297              usual.
298    
299        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
300              and 16-bit fields in a compiled pattern, to simulate a pattern that
301              was compiled on a host of opposite endianness.
302    
303    21. The pcre-exec() function can now cope with patterns that were compiled on
304        hosts of opposite endianness, with this restriction:
305    
306          As for any compiled expression that is saved and used later, the tables
307          pointer field cannot be preserved; the extra_data field in the arguments
308          to pcre_exec() should be used to pass in a tables address if a value
309          other than the default internal tables were used at compile time.
310    
311    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
312        now diagnosed as an error. Previously, most of the time, a negative number
313        would have been treated as zero, but if in addition "ovector" was passed as
314        NULL, a crash could occur.
315    
316    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
317        new versions from the libtool 1.5 distribution (the last one is a copy of
318        a file called libtool.m4). This seems to have fixed the need to patch
319        "configure" to support Darwin 1.3 (which I used to do). However, I still
320        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
321        workstation).
322    
323    24. Changed the PCRE licence to be the more standard "BSD" licence.
324    
325    
326    Version 4.5 01-Dec-03
327    ---------------------
328    
329     1. There has been some re-arrangement of the code for the match() function so
330        that it can be compiled in a version that does not call itself recursively.
331        Instead, it keeps those local variables that need separate instances for
332        each "recursion" in a frame on the heap, and gets/frees frames whenever it
333        needs to "recurse". Keeping track of where control must go is done by means
334        of setjmp/longjmp. The whole thing is implemented by a set of macros that
335        hide most of the details from the main code, and operates only if
336        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
337        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
338        operating.
339    
340        To make it easier for callers to provide specially tailored get/free
341        functions for this usage, two new functions, pcre_stack_malloc, and
342        pcre_stack_free, are used. They are always called in strict stacking order,
343        and the size of block requested is always the same.
344    
345        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
346        PCRE has been compiled to use the stack or the heap for recursion. The
347        -C option of pcretest uses this to show which version is compiled.
348    
349        A new data escape \S, is added to pcretest; it causes the amounts of store
350        obtained and freed by both kinds of malloc/free at match time to be added
351        to the output.
352    
353     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
354        what's available on my current Linux desktop machine.
355    
356     3. When matching a UTF-8 string, the test for a valid string at the start has
357        been extended. If start_offset is not zero, PCRE now checks that it points
358        to a byte that is the start of a UTF-8 character. If not, it returns
359        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
360        this is necessary because there may be backward assertions in the pattern.
361        When matching the same subject several times, it may save resources to use
362        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
363    
364     4. The code for checking the validity of UTF-8 strings has been tightened so
365        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
366        containing "overlong sequences".
367    
368     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
369        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
370        should have been "&", but it just so happened that all the cases this let
371        through by mistake were picked up later in the function.
372    
373     6. I had used a variable called "isblank" - this is a C99 function, causing
374        some compilers to warn. To avoid this, I renamed it (as "blankclass").
375    
376     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
377        prompting; (b) run "./pcretest /dev/null" at the start of the test script
378        so the version is shown; (c) stop "make test" echoing "./RunTest".
379    
380     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
381    
382     9. The prototype for memmove() for systems that don't have it was using
383        size_t, but the inclusion of the header that defines size_t was later. I've
384        moved the #includes for the C headers earlier to avoid this.
385    
386    10. Added some adjustments to the code to make it easier to compiler on certain
387        special systems:
388    
389          (a) Some "const" qualifiers were missing.
390          (b) Added the macro EXPORT before all exported functions; by default this
391              is defined to be empty.
392          (c) Changed the dftables auxiliary program (that builds chartables.c) so
393              that it reads its output file name as an argument instead of writing
394              to the standard output and assuming this can be redirected.
395    
396    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
397        class containing characters with values greater than 255, PCRE compilation
398        went into a loop.
399    
400    12. A recursive reference to a subpattern that was within another subpattern
401        that had a minimum quantifier of zero caused PCRE to crash. For example,
402        (x(y(?2))z)? provoked this bug with a subject that got as far as the
403        recursion. If the recursively-called subpattern itself had a zero repeat,
404        that was OK.
405    
406    13. In pcretest, the buffer for reading a data line was set at 30K, but the
407        buffer into which it was copied (for escape processing) was still set at
408        1024, so long lines caused crashes.
409    
410    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
411        "internal error: code overflow...". This applied to any character class
412        that was followed by a possessive quantifier.
413    
414    15. Modified the Makefile to add libpcre.la as a prerequisite for
415        libpcreposix.la because I was told this is needed for a parallel build to
416        work.
417    
418    16. If a pattern that contained .* following optional items at the start was
419        studied, the wrong optimizing data was generated, leading to matching
420        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
421        matching string must start with a or b or c. The correct conclusion for
422        this pattern is that a match can start with any character.
423    
424    
425    Version 4.4 13-Aug-03
426    ---------------------
427    
428     1. In UTF-8 mode, a character class containing characters with values between
429        127 and 255 was not handled correctly if the compiled pattern was studied.
430        In fixing this, I have also improved the studying algorithm for such
431        classes (slightly).
432    
433     2. Three internal functions had redundant arguments passed to them. Removal
434        might give a very teeny performance improvement.
435    
436     3. Documentation bug: the value of the capture_top field in a callout is *one
437        more than* the number of the hightest numbered captured substring.
438    
439     4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
440        in incorrectly linking with a previously installed version. They now link
441        explicitly with libpcre.la.
442    
443     5. configure.in no longer needs to recognize Cygwin specially.
444    
445     6. A problem in pcre.in for Windows platforms is fixed.
446    
447     7. If a pattern was successfully studied, and the -d (or /D) flag was given to
448        pcretest, it used to include the size of the study block as part of its
449        output. Unfortunately, the structure contains a field that has a different
450        size on different hardware architectures. This meant that the tests that
451        showed this size failed. As the block is currently always of a fixed size,
452        this information isn't actually particularly useful in pcretest output, so
453        I have just removed it.
454    
455     8. Three pre-processor statements accidentally did not start in column 1.
456        Sadly, there are *still* compilers around that complain, even though
457        standard C has not required this for well over a decade. Sigh.
458    
459     9. In pcretest, the code for checking callouts passed small integers in the
460        callout_data field, which is a void * field. However, some picky compilers
461        complained about the casts involved for this on 64-bit systems. Now
462        pcretest passes the address of the small integer instead, which should get
463        rid of the warnings.
464    
465    10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
466        both compile and run time, and gives an error if an invalid UTF-8 sequence
467        is found. There is a option for disabling this check in cases where the
468        string is known to be correct and/or the maximum performance is wanted.
469    
470    11. In response to a bug report, I changed one line in Makefile.in from
471    
472            -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
473        to
474            -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
475    
476        to look similar to other lines, but I have no way of telling whether this
477        is the right thing to do, as I do not use Windows. No doubt I'll get told
478        if it's wrong...
479    
480    
481    Version 4.3 21-May-03
482    ---------------------
483    
484    1. Two instances of @WIN_PREFIX@ omitted from the Windows targets in the
485       Makefile.
486    
487    2. Some refactoring to improve the quality of the code:
488    
489       (i)   The utf8_table... variables are now declared "const".
490    
491       (ii)  The code for \cx, which used the "case flipping" table to upper case
492             lower case letters, now just substracts 32. This is ASCII-specific,
493             but the whole concept of \cx is ASCII-specific, so it seems
494             reasonable.
495    
496       (iii) PCRE was using its character types table to recognize decimal and
497             hexadecimal digits in the pattern. This is silly, because it handles
498             only 0-9, a-f, and A-F, but the character types table is locale-
499             specific, which means strange things might happen. A private
500             table is now used for this - though it costs 256 bytes, a table is
501             much faster than multiple explicit tests. Of course, the standard
502             character types table is still used for matching digits in subject
503             strings against \d.
504    
505       (iv)  Strictly, the identifier ESC_t is reserved by POSIX (all identifiers
506             ending in _t are). So I've renamed it as ESC_tee.
507    
508    3. The first argument for regexec() in the POSIX wrapper should have been
509       defined as "const".
510    
511    4. Changed pcretest to use malloc() for its buffers so that they can be
512       Electric Fenced for debugging.
513    
514    5. There were several places in the code where, in UTF-8 mode, PCRE would try
515       to read one or more bytes before the start of the subject string. Often this
516       had no effect on PCRE's behaviour, but in some circumstances it could
517       provoke a segmentation fault.
518    
519    6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
520       to try to read one or more bytes before the start of the subject string.
521    
522    7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
523       UTF-8 support could misbehave in various ways if the subject string
524       contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
525       area. (PCRE was not checking for the UTF-8 mode flag, and trying to move
526       back over UTF-8 characters.)
527    
528    
529    Version 4.2 14-Apr-03
530    ---------------------
531    
532    1. Typo "#if SUPPORT_UTF8" instead of "#ifdef SUPPORT_UTF8" fixed.
533    
534    2. Changes to the building process, supplied by Ronald Landheer-Cieslak
535         [ON_WINDOWS]: new variable, "#" on non-Windows platforms
536         [NOT_ON_WINDOWS]: new variable, "#" on Windows platforms
537         [WIN_PREFIX]: new variable, "cyg" for Cygwin
538         * Makefile.in: use autoconf substitution for OBJEXT, EXEEXT, BUILD_OBJEXT
539           and BUILD_EXEEXT
540         Note: automatic setting of the BUILD variables is not yet working
541         set CPPFLAGS and BUILD_CPPFLAGS (but don't use yet) - should be used at
542           compile-time but not at link-time
543         [LINK]: use for linking executables only
544         make different versions for Windows and non-Windows
545         [LINKLIB]: new variable, copy of UNIX-style LINK, used for linking
546           libraries
547         [LINK_FOR_BUILD]: new variable
548         [OBJEXT]: use throughout
549         [EXEEXT]: use throughout
550         <winshared>: new target
551         <wininstall>: new target
552         <dftables.o>: use native compiler
553         <dftables>: use native linker
554         <install>: handle Windows platform correctly
555         <clean>: ditto
556         <check>: ditto
557         copy DLL to top builddir before testing
558    
559       As part of these changes, -no-undefined was removed again. This was reported
560       to give trouble on HP-UX 11.0, so getting rid of it seems like a good idea
561       in any case.
562    
563    3. Some tidies to get rid of compiler warnings:
564    
565       . In the match_data structure, match_limit was an unsigned long int, whereas
566         match_call_count was an int. I've made them both unsigned long ints.
567    
568       . In pcretest the fact that a const uschar * doesn't automatically cast to
569         a void * provoked a warning.
570    
571       . Turning on some more compiler warnings threw up some "shadow" variables
572         and a few more missing casts.
573    
574    4. If PCRE was complied with UTF-8 support, but called without the PCRE_UTF8
575       option, a class that contained a single character with a value between 128
576       and 255 (e.g. /[\xFF]/) caused PCRE to crash.
577    
578    5. If PCRE was compiled with UTF-8 support, but called without the PCRE_UTF8
579       option, a class that contained several characters, but with at least one
580       whose value was between 128 and 255 caused PCRE to crash.
581    
582    
583    Version 4.1 12-Mar-03
584    ---------------------
585    
586    1. Compiling with gcc -pedantic found a couple of places where casts were
587    needed, and a string in dftables.c that was longer than standard compilers are
588    required to support.
589    
590    2. Compiling with Sun's compiler found a few more places where the code could
591    be tidied up in order to avoid warnings.
592    
593    3. The variables for cross-compiling were called HOST_CC and HOST_CFLAGS; the
594    first of these names is deprecated in the latest Autoconf in favour of the name
595    CC_FOR_BUILD, because "host" is typically used to mean the system on which the
596    compiled code will be run. I can't find a reference for HOST_CFLAGS, but by
597    analogy I have changed it to CFLAGS_FOR_BUILD.
598    
599    4. Added -no-undefined to the linking command in the Makefile, because this is
600    apparently helpful for Windows. To make it work, also added "-L. -lpcre" to the
601    linking step for the pcreposix library.
602    
603    5. PCRE was failing to diagnose the case of two named groups with the same
604    name.
605    
606    6. A problem with one of PCRE's optimizations was discovered. PCRE remembers a
607    literal character that is needed in the subject for a match, and scans along to
608    ensure that it is present before embarking on the full matching process. This
609    saves time in cases of nested unlimited repeats that are never going to match.
610    Problem: the scan can take a lot of time if the subject is very long (e.g.
611    megabytes), thus penalizing straightforward matches. It is now done only if the
612    amount of subject to be scanned is less than 1000 bytes.
613    
614    7. A lesser problem with the same optimization is that it was recording the
615    first character of an anchored pattern as "needed", thus provoking a search
616    right along the subject, even when the first match of the pattern was going to
617    fail. The "needed" character is now not set for anchored patterns, unless it
618    follows something in the pattern that is of non-fixed length. Thus, it still
619    fulfils its original purpose of finding quick non-matches in cases of nested
620    unlimited repeats, but isn't used for simple anchored patterns such as /^abc/.
621    
622    
623    Version 4.0 17-Feb-03
624    ---------------------
625    
626    1. If a comment in an extended regex that started immediately after a meta-item
627    extended to the end of string, PCRE compiled incorrect data. This could lead to
628    all kinds of weird effects. Example: /#/ was bad; /()#/ was bad; /a#/ was not.
629    
630    2. Moved to autoconf 2.53 and libtool 1.4.2.
631    
632    3. Perl 5.8 no longer needs "use utf8" for doing UTF-8 things. Consequently,
633    the special perltest8 script is no longer needed - all the tests can be run
634    from a single perltest script.
635    
636    4. From 5.004, Perl has not included the VT character (0x0b) in the set defined
637    by \s. It has now been removed in PCRE. This means it isn't recognized as
638    whitespace in /x regexes too, which is the same as Perl. Note that the POSIX
639    class [:space:] *does* include VT, thereby creating a mess.
640    
641    5. Added the class [:blank:] (a GNU extension from Perl 5.8) to match only
642    space and tab.
643    
644    6. Perl 5.005 was a long time ago. It's time to amalgamate the tests that use
645    its new features into the main test script, reducing the number of scripts.
646    
647    7. Perl 5.8 has changed the meaning of patterns like /a(?i)b/. Earlier versions
648    were backward compatible, and made the (?i) apply to the whole pattern, as if
649    /i were given. Now it behaves more logically, and applies the option setting
650    only to what follows. PCRE has been changed to follow suit. However, if it
651    finds options settings right at the start of the pattern, it extracts them into
652    the global options, as before. Thus, they show up in the info data.
653    
654    8. Added support for the \Q...\E escape sequence. Characters in between are
655    treated as literals. This is slightly different from Perl in that $ and @ are
656    also handled as literals inside the quotes. In Perl, they will cause variable
657    interpolation. Note the following examples:
658    
659        Pattern            PCRE matches      Perl matches
660    
661        \Qabc$xyz\E        abc$xyz           abc followed by the contents of $xyz
662        \Qabc\$xyz\E       abc\$xyz          abc\$xyz
663        \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz
664    
665    For compatibility with Perl, \Q...\E sequences are recognized inside character
666    classes as well as outside them.
667    
668    9. Re-organized 3 code statements in pcretest to avoid "overflow in
669    floating-point constant arithmetic" warnings from a Microsoft compiler. Added a
670    (size_t) cast to one statement in pcretest and one in pcreposix to avoid
671    signed/unsigned warnings.
672    
673    10. SunOS4 doesn't have strtoul(). This was used only for unpicking the -o
674    option for pcretest, so I've replaced it by a simple function that does just
675    that job.
676    
677    11. pcregrep was ending with code 0 instead of 2 for the commands "pcregrep" or
678    "pcregrep -".
679    
680    12. Added "possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's
681    Java package. This provides some syntactic sugar for simple cases of what my
682    documentation calls "once-only subpatterns". A pattern such as x*+ is the same
683    as (?>x*). In other words, if what is inside (?>...) is just a single repeated
684    item, you can use this simplified notation. Note that only makes sense with
685    greedy quantifiers. Consequently, the use of the possessive quantifier forces
686    greediness, whatever the setting of the PCRE_UNGREEDY option.
687    
688    13. A change of greediness default within a pattern was not taking effect at
689    the current level for patterns like /(b+(?U)a+)/. It did apply to parenthesized
690    subpatterns that followed. Patterns like /b+(?U)a+/ worked because the option
691    was abstracted outside.
692    
693    14. PCRE now supports the \G assertion. It is true when the current matching
694    position is at the start point of the match. This differs from \A when the
695    starting offset is non-zero. Used with the /g option of pcretest (or similar
696    code), it works in the same way as it does for Perl's /g option. If all
697    alternatives of a regex begin with \G, the expression is anchored to the start
698    match position, and the "anchored" flag is set in the compiled expression.
699    
700    15. Some bugs concerning the handling of certain option changes within patterns
701    have been fixed. These applied to options other than (?ims). For example,
702    "a(?x: b c )d" did not match "XabcdY" but did match "Xa b c dY". It should have
703    been the other way round. Some of this was related to change 7 above.
704    
705    16. PCRE now gives errors for /[.x.]/ and /[=x=]/ as unsupported POSIX
706    features, as Perl does. Previously, PCRE gave the warnings only for /[[.x.]]/
707    and /[[=x=]]/. PCRE now also gives an error for /[:name:]/ because it supports
708    POSIX classes only within a class (e.g. /[[:alpha:]]/).
709    
710    17. Added support for Perl's \C escape. This matches one byte, even in UTF8
711    mode. Unlike ".", it always matches newline, whatever the setting of
712    PCRE_DOTALL. However, PCRE does not permit \C to appear in lookbehind
713    assertions. Perl allows it, but it doesn't (in general) work because it can't
714    calculate the length of the lookbehind. At least, that's the case for Perl
715    5.8.0 - I've been told they are going to document that it doesn't work in
716    future.
717    
718    18. Added an error diagnosis for escapes that PCRE does not support: these are
719    \L, \l, \N, \P, \p, \U, \u, and \X.
720    
721    19. Although correctly diagnosing a missing ']' in a character class, PCRE was
722    reading past the end of the pattern in cases such as /[abcd/.
723    
724    20. PCRE was getting more memory than necessary for patterns with classes that
725    contained both POSIX named classes and other characters, e.g. /[[:space:]abc/.
726    
727    21. Added some code, conditional on #ifdef VPCOMPAT, to make life easier for
728    compiling PCRE for use with Virtual Pascal.
729    
730    22. Small fix to the Makefile to make it work properly if the build is done
731    outside the source tree.
732    
733    23. Added a new extension: a condition to go with recursion. If a conditional
734    subpattern starts with (?(R) the "true" branch is used if recursion has
735    happened, whereas the "false" branch is used only at the top level.
736    
737    24. When there was a very long string of literal characters (over 255 bytes
738    without UTF support, over 250 bytes with UTF support), the computation of how
739    much memory was required could be incorrect, leading to segfaults or other
740    strange effects.
741    
742    25. PCRE was incorrectly assuming anchoring (either to start of subject or to
743    start of line for a non-DOTALL pattern) when a pattern started with (.*) and
744    there was a subsequent back reference to those brackets. This meant that, for
745    example, /(.*)\d+\1/ failed to match "abc123bc". Unfortunately, it isn't
746    possible to check for precisely this case. All we can do is abandon the
747    optimization if .* occurs inside capturing brackets when there are any back
748    references whatsoever. (See below for a better fix that came later.)
749    
750    26. The handling of the optimization for finding the first character of a
751    non-anchored pattern, and for finding a character that is required later in the
752    match were failing in some cases. This didn't break the matching; it just
753    failed to optimize when it could. The way this is done has been re-implemented.
754    
755    27. Fixed typo in error message for invalid (?R item (it said "(?p").
756    
757    28. Added a new feature that provides some of the functionality that Perl
758    provides with (?{...}). The facility is termed a "callout". The way it is done
759    in PCRE is for the caller to provide an optional function, by setting
760    pcre_callout to its entry point. Like pcre_malloc and pcre_free, this is a
761    global variable. By default it is unset, which disables all calling out. To get
762    the function called, the regex must include (?C) at appropriate points. This
763    is, in fact, equivalent to (?C0), and any number <= 255 may be given with (?C).
764    This provides a means of identifying different callout points. When PCRE
765    reaches such a point in the regex, if pcre_callout has been set, the external
766    function is called. It is provided with data in a structure called
767    pcre_callout_block, which is defined in pcre.h. If the function returns 0,
768    matching continues; if it returns a non-zero value, the match at the current
769    point fails. However, backtracking will occur if possible. [This was changed
770    later and other features added - see item 49 below.]
771    
772    29. pcretest is upgraded to test the callout functionality. It provides a
773    callout function that displays information. By default, it shows the start of
774    the match and the current position in the text. There are some new data escapes
775    to vary what happens:
776    
777        \C+         in addition, show current contents of captured substrings
778        \C-         do not supply a callout function
779        \C!n        return 1 when callout number n is reached
780        \C!n!m      return 1 when callout number n is reached for the mth time
781    
782    30. If pcregrep was called with the -l option and just a single file name, it
783    output "<stdin>" if a match was found, instead of the file name.
784    
785    31. Improve the efficiency of the POSIX API to PCRE. If the number of capturing
786    slots is less than POSIX_MALLOC_THRESHOLD, use a block on the stack to pass to
787    pcre_exec(). This saves a malloc/free per call. The default value of
788    POSIX_MALLOC_THRESHOLD is 10; it can be changed by --with-posix-malloc-threshold
789    when configuring.
790    
791    32. The default maximum size of a compiled pattern is 64K. There have been a
792    few cases of people hitting this limit. The code now uses macros to handle the
793    storing of links as offsets within the compiled pattern. It defaults to 2-byte
794    links, but this can be changed to 3 or 4 bytes by --with-link-size when
795    configuring. Tests 2 and 5 work only with 2-byte links because they output
796    debugging information about compiled patterns.
797    
798    33. Internal code re-arrangements:
799    
800    (a) Moved the debugging function for printing out a compiled regex into
801        its own source file (printint.c) and used #include to pull it into
802        pcretest.c and, when DEBUG is defined, into pcre.c, instead of having two
803        separate copies.
804    
805    (b) Defined the list of op-code names for debugging as a macro in
806        internal.h so that it is next to the definition of the opcodes.
807    
808    (c) Defined a table of op-code lengths for simpler skipping along compiled
809        code. This is again a macro in internal.h so that it is next to the
810        definition of the opcodes.
811    
812    34. Added support for recursive calls to individual subpatterns, along the
813    lines of Robin Houston's patch (but implemented somewhat differently).
814    
815    35. Further mods to the Makefile to help Win32. Also, added code to pcregrep to
816    allow it to read and process whole directories in Win32. This code was
817    contributed by Lionel Fourquaux; it has not been tested by me.
818    
819    36. Added support for named subpatterns. The Python syntax (?P<name>...) is
820    used to name a group. Names consist of alphanumerics and underscores, and must
821    be unique. Back references use the syntax (?P=name) and recursive calls use
822    (?P>name) which is a PCRE extension to the Python extension. Groups still have
823    numbers. The function pcre_fullinfo() can be used after compilation to extract
824    a name/number map. There are three relevant calls:
825    
826      PCRE_INFO_NAMEENTRYSIZE        yields the size of each entry in the map
827      PCRE_INFO_NAMECOUNT            yields the number of entries
828      PCRE_INFO_NAMETABLE            yields a pointer to the map.
829    
830    The map is a vector of fixed-size entries. The size of each entry depends on
831    the length of the longest name used. The first two bytes of each entry are the
832    group number, most significant byte first. There follows the corresponding
833    name, zero terminated. The names are in alphabetical order.
834    
835    37. Make the maximum literal string in the compiled code 250 for the non-UTF-8
836    case instead of 255. Making it the same both with and without UTF-8 support
837    means that the same test output works with both.
838    
839    38. There was a case of malloc(0) in the POSIX testing code in pcretest. Avoid
840    calling malloc() with a zero argument.
841    
842    39. Change 25 above had to resort to a heavy-handed test for the .* anchoring
843    optimization. I've improved things by keeping a bitmap of backreferences with
844    numbers 1-31 so that if .* occurs inside capturing brackets that are not in
845    fact referenced, the optimization can be applied. It is unlikely that a
846    relevant occurrence of .* (i.e. one which might indicate anchoring or forcing
847    the match to follow \n) will appear inside brackets with a number greater than
848    31, but if it does, any back reference > 31 suppresses the optimization.
849    
850    40. Added a new compile-time option PCRE_NO_AUTO_CAPTURE. This has the effect
851    of disabling numbered capturing parentheses. Any opening parenthesis that is
852    not followed by ? behaves as if it were followed by ?: but named parentheses
853    can still be used for capturing (and they will acquire numbers in the usual
854    way).
855    
856    41. Redesigned the return codes from the match() function into yes/no/error so
857    that errors can be passed back from deep inside the nested calls. A malloc
858    failure while inside a recursive subpattern call now causes the
859    PCRE_ERROR_NOMEMORY return instead of quietly going wrong.
860    
861    42. It is now possible to set a limit on the number of times the match()
862    function is called in a call to pcre_exec(). This facility makes it possible to
863    limit the amount of recursion and backtracking, though not in a directly
864    obvious way, because the match() function is used in a number of different
865    circumstances. The count starts from zero for each position in the subject
866    string (for non-anchored patterns). The default limit is, for compatibility, a
867    large number, namely 10 000 000. You can change this in two ways:
868    
869    (a) When configuring PCRE before making, you can use --with-match-limit=n
870        to set a default value for the compiled library.
871    
872    (b) For each call to pcre_exec(), you can pass a pcre_extra block in which
873        a different value is set. See 45 below.
874    
875    If the limit is exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
876    
877    43. Added a new function pcre_config(int, void *) to enable run-time extraction
878    of things that can be changed at compile time. The first argument specifies
879    what is wanted and the second points to where the information is to be placed.
880    The current list of available information is:
881    
882      PCRE_CONFIG_UTF8
883    
884    The output is an integer that is set to one if UTF-8 support is available;
885    otherwise it is set to zero.
886    
887      PCRE_CONFIG_NEWLINE
888    
889    The output is an integer that it set to the value of the code that is used for
890    newline. It is either LF (10) or CR (13).
891    
892      PCRE_CONFIG_LINK_SIZE
893    
894    The output is an integer that contains the number of bytes used for internal
895    linkage in compiled expressions. The value is 2, 3, or 4. See item 32 above.
896    
897      PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
898    
899    The output is an integer that contains the threshold above which the POSIX
900    interface uses malloc() for output vectors. See item 31 above.
901    
902      PCRE_CONFIG_MATCH_LIMIT
903    
904    The output is an unsigned integer that contains the default limit of the number
905    of match() calls in a pcre_exec() execution. See 42 above.
906    
907    44. pcretest has been upgraded by the addition of the -C option. This causes it
908    to extract all the available output from the new pcre_config() function, and to
909    output it. The program then exits immediately.
910    
911    45. A need has arisen to pass over additional data with calls to pcre_exec() in
912    order to support additional features. One way would have been to define
913    pcre_exec2() (for example) with extra arguments, but this would not have been
914    extensible, and would also have required all calls to the original function to
915    be mapped to the new one. Instead, I have chosen to extend the mechanism that
916    is used for passing in "extra" data from pcre_study().
917    
918    The pcre_extra structure is now exposed and defined in pcre.h. It currently
919    contains the following fields:
920    
921      flags         a bitmap indicating which of the following fields are set
922      study_data    opaque data from pcre_study()
923      match_limit   a way of specifying a limit on match() calls for a specific
924                      call to pcre_exec()
925      callout_data  data for callouts (see 49 below)
926    
927    The flag bits are also defined in pcre.h, and are
928    
929      PCRE_EXTRA_STUDY_DATA
930      PCRE_EXTRA_MATCH_LIMIT
931      PCRE_EXTRA_CALLOUT_DATA
932    
933    The pcre_study() function now returns one of these new pcre_extra blocks, with
934    the actual study data pointed to by the study_data field, and the
935    PCRE_EXTRA_STUDY_DATA flag set. This can be passed directly to pcre_exec() as
936    before. That is, this change is entirely upwards-compatible and requires no
937    change to existing code.
938    
939    If you want to pass in additional data to pcre_exec(), you can either place it
940    in a pcre_extra block provided by pcre_study(), or create your own pcre_extra
941    block.
942    
943    46. pcretest has been extended to test the PCRE_EXTRA_MATCH_LIMIT feature. If a
944    data string contains the escape sequence \M, pcretest calls pcre_exec() several
945    times with different match limits, until it finds the minimum value needed for
946    pcre_exec() to complete. The value is then output. This can be instructive; for
947    most simple matches the number is quite small, but for pathological cases it
948    gets very large very quickly.
949    
950    47. There's a new option for pcre_fullinfo() called PCRE_INFO_STUDYSIZE. It
951    returns the size of the data block pointed to by the study_data field in a
952    pcre_extra block, that is, the value that was passed as the argument to
953    pcre_malloc() when PCRE was getting memory in which to place the information
954    created by pcre_study(). The fourth argument should point to a size_t variable.
955    pcretest has been extended so that this information is shown after a successful
956    pcre_study() call when information about the compiled regex is being displayed.
957    
958    48. Cosmetic change to Makefile: there's no need to have / after $(DESTDIR)
959    because what follows is always an absolute path. (Later: it turns out that this
960    is more than cosmetic for MinGW, because it doesn't like empty path
961    components.)
962    
963    49. Some changes have been made to the callout feature (see 28 above):
964    
965    (i)  A callout function now has three choices for what it returns:
966    
967           0  =>  success, carry on matching
968         > 0  =>  failure at this point, but backtrack if possible
969         < 0  =>  serious error, return this value from pcre_exec()
970    
971         Negative values should normally be chosen from the set of PCRE_ERROR_xxx
972         values. In particular, returning PCRE_ERROR_NOMATCH forces a standard
973         "match failed" error. The error number PCRE_ERROR_CALLOUT is reserved for
974         use by callout functions. It will never be used by PCRE itself.
975    
976    (ii) The pcre_extra structure (see 45 above) has a void * field called
977         callout_data, with corresponding flag bit PCRE_EXTRA_CALLOUT_DATA. The
978         pcre_callout_block structure has a field of the same name. The contents of
979         the field passed in the pcre_extra structure are passed to the callout
980         function in the corresponding field in the callout block. This makes it
981         easier to use the same callout-containing regex from multiple threads. For
982         testing, the pcretest program has a new data escape
983    
984           \C*n        pass the number n (may be negative) as callout_data
985    
986         If the callout function in pcretest receives a non-zero value as
987         callout_data, it returns that value.
988    
989    50. Makefile wasn't handling CFLAGS properly when compiling dftables. Also,
990    there were some redundant $(CFLAGS) in commands that are now specified as
991    $(LINK), which already includes $(CFLAGS).
992    
993    51. Extensions to UTF-8 support are listed below. These all apply when (a) PCRE
994    has been compiled with UTF-8 support *and* pcre_compile() has been compiled
995    with the PCRE_UTF8 flag. Patterns that are compiled without that flag assume
996    one-byte characters throughout. Note that case-insensitive matching applies
997    only to characters whose values are less than 256. PCRE doesn't support the
998    notion of cases for higher-valued characters.
999    
1000    (i)   A character class whose characters are all within 0-255 is handled as
1001          a bit map, and the map is inverted for negative classes. Previously, a
1002          character > 255 always failed to match such a class; however it should
1003          match if the class was a negative one (e.g. [^ab]). This has been fixed.
1004    
1005    (ii)  A negated character class with a single character < 255 is coded as
1006          "not this character" (OP_NOT). This wasn't working properly when the test
1007          character was multibyte, either singly or repeated.
1008    
1009    (iii) Repeats of multibyte characters are now handled correctly in UTF-8
1010          mode, for example: \x{100}{2,3}.
1011    
1012    (iv)  The character escapes \b, \B, \d, \D, \s, \S, \w, and \W (either
1013          singly or repeated) now correctly test multibyte characters. However,
1014          PCRE doesn't recognize any characters with values greater than 255 as
1015          digits, spaces, or word characters. Such characters always match \D, \S,
1016          and \W, and never match \d, \s, or \w.
1017    
1018    (v)   Classes may now contain characters and character ranges with values
1019          greater than 255. For example: [ab\x{100}-\x{400}].
1020    
1021    (vi)  pcregrep now has a --utf-8 option (synonym -u) which makes it call
1022          PCRE in UTF-8 mode.
1023    
1024    52. The info request value PCRE_INFO_FIRSTCHAR has been renamed
1025    PCRE_INFO_FIRSTBYTE because it is a byte value. However, the old name is
1026    retained for backwards compatibility. (Note that LASTLITERAL is also a byte
1027    value.)
1028    
1029    53. The single man page has become too large. I have therefore split it up into
1030    a number of separate man pages. These also give rise to individual HTML pages;
1031    these are now put in a separate directory, and there is an index.html page that
1032    lists them all. Some hyperlinking between the pages has been installed.
1033    
1034    54. Added convenience functions for handling named capturing parentheses.
1035    
1036    55. Unknown escapes inside character classes (e.g. [\M]) and escapes that
1037    aren't interpreted therein (e.g. [\C]) are literals in Perl. This is now also
1038    true in PCRE, except when the PCRE_EXTENDED option is set, in which case they
1039    are faulted.
1040    
1041    56. Introduced HOST_CC and HOST_CFLAGS which can be set in the environment when
1042    calling configure. These values are used when compiling the dftables.c program
1043    which is run to generate the source of the default character tables. They
1044    default to the values of CC and CFLAGS. If you are cross-compiling PCRE,
1045    you will need to set these values.
1046    
1047    57. Updated the building process for Windows DLL, as provided by Fred Cox.
1048    
1049    
1050    Version 3.9 02-Jan-02
1051    ---------------------
1052    
1053    1. A bit of extraneous text had somehow crept into the pcregrep documentation.
1054    
1055    2. If --disable-static was given, the building process failed when trying to
1056    build pcretest and pcregrep. (For some reason it was using libtool to compile
1057    them, which is not right, as they aren't part of the library.)
1058    
1059    
1060    Version 3.8 18-Dec-01
1061    ---------------------
1062    
1063    1. The experimental UTF-8 code was completely screwed up. It was packing the
1064    bytes in the wrong order. How dumb can you get?
1065    
1066    
1067    Version 3.7 29-Oct-01
1068    ---------------------
1069    
1070    1. In updating pcretest to check change 1 of version 3.6, I screwed up.
1071    This caused pcretest, when used on the test data, to segfault. Unfortunately,
1072    this didn't happen under Solaris 8, where I normally test things.
1073    
1074    2. The Makefile had to be changed to make it work on BSD systems, where 'make'
1075    doesn't seem to recognize that ./xxx and xxx are the same file. (This entry
1076    isn't in ChangeLog distributed with 3.7 because I forgot when I hastily made
1077    this fix an hour or so after the initial 3.7 release.)
1078    
1079    
1080    Version 3.6 23-Oct-01
1081    ---------------------
1082    
1083    1. Crashed with /(sens|respons)e and \1ibility/ and "sense and sensibility" if
1084    offsets passed as NULL with zero offset count.
1085    
1086    2. The config.guess and config.sub files had not been updated when I moved to
1087    the latest autoconf.
1088    
1089    
1090    Version 3.5 15-Aug-01
1091    ---------------------
1092    
1093    1. Added some missing #if !defined NOPOSIX conditionals in pcretest.c that
1094    had been forgotten.
1095    
1096    2. By using declared but undefined structures, we can avoid using "void"
1097    definitions in pcre.h while keeping the internal definitions of the structures
1098    private.
1099    
1100    3. The distribution is now built using autoconf 2.50 and libtool 1.4. From a
1101    user point of view, this means that both static and shared libraries are built
1102    by default, but this can be individually controlled. More of the work of
1103    handling this static/shared cases is now inside libtool instead of PCRE's make
1104    file.
1105    
1106    4. The pcretest utility is now installed along with pcregrep because it is
1107    useful for users (to test regexs) and by doing this, it automatically gets
1108    relinked by libtool. The documentation has been turned into a man page, so
1109    there are now .1, .txt, and .html versions in /doc.
1110    
1111    5. Upgrades to pcregrep:
1112       (i)   Added long-form option names like gnu grep.
1113       (ii)  Added --help to list all options with an explanatory phrase.
1114       (iii) Added -r, --recursive to recurse into sub-directories.
1115       (iv)  Added -f, --file to read patterns from a file.
1116    
1117    6. pcre_exec() was referring to its "code" argument before testing that
1118    argument for NULL (and giving an error if it was NULL).
1119    
1120    7. Upgraded Makefile.in to allow for compiling in a different directory from
1121    the source directory.
1122    
1123    8. Tiny buglet in pcretest: when pcre_fullinfo() was called to retrieve the
1124    options bits, the pointer it was passed was to an int instead of to an unsigned
1125    long int. This mattered only on 64-bit systems.
1126    
1127    9. Fixed typo (3.4/1) in pcre.h again. Sigh. I had changed pcre.h (which is
1128    generated) instead of pcre.in, which it its source. Also made the same change
1129    in several of the .c files.
1130    
1131    10. A new release of gcc defines printf() as a macro, which broke pcretest
1132    because it had an ifdef in the middle of a string argument for printf(). Fixed
1133    by using separate calls to printf().
1134    
1135    11. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure
1136    script, to force use of CR or LF instead of \n in the source. On non-Unix
1137    systems, the value can be set in config.h.
1138    
1139    12. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an
1140    absolute limit. Changed the text of the error message to make this clear, and
1141    likewise updated the man page.
1142    
1143    13. The limit of 99 on the number of capturing subpatterns has been removed.
1144    The new limit is 65535, which I hope will not be a "real" limit.
1145    
1146    
1147  Version 3.4 22-Aug-00  Version 3.4 22-Aug-00
1148  ---------------------  ---------------------

Legend:
Removed from v.51  
changed lines
  Added in v.79

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12