ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 143 by ph10, Mon Apr 2 10:08:14 2007 UTC revision 329 by ph10, Fri Mar 28 12:06:36 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-07  Version 7.7 05-Mar-08
5    ---------------------
7    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
8        a string to a long long, pretend we don't even have a long long." This is
9        done by checking for the strtoq, strtoll, and _strtoi64 functions.
11    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
12        pre-7.6 versions, which defined a global no_arg variable instead of putting
13        it in the RE class.
15    3.  Remove a line of dead code, identified by coverity and reported by Nuno
16        Lopes.
18    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
20        (1) The include/exclude patterns were being applied to the whole pathnames
21            of files, instead of just to the final components.
23        (2) If there was more than one level of directory, the subdirectories were
24            skipped unless they satisfied the include/exclude conditions. This is
25            inconsistent with GNU grep (and could even be seen as contrary to the
26            pcregrep specification - which I improved to make it absolutely clear).
27            The action now is always to scan all levels of directory, and just
28            apply the include/exclude patterns to regular files.
30    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
31        --exclude_dir in the tests to avoid scanning .svn directories.
33    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
34        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
35        doesn't support NULs in patterns.
37    7.  Added some missing "const"s to declarations of static tables in
38        pcre_compile.c and pcre_dfa_exec.c.
40    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above. (Subsequently also a second patch to fix the
42        first patch.)
45    Version 7.6 28-Jan-08
46    ---------------------
48    1.  A character class containing a very large number of characters with
49        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
50        overflow.
52    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
53        HAVE_LONG_LONG is not defined.
55    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
56        bring them up to date and include new features. This patch includes:
58        - Fixed PH's badly added libz and libbz2 support.
59        - Fixed a problem with static linking.
60        - Added pcredemo. [But later removed - see 7 below.]
61        - Fixed dftables problem and added an option.
62        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
63            HAVE_LONG_LONG.
64        - Added readline support for pcretest.
65        - Added an listing of the option settings after cmake has run.
67    4.  A user submitted a patch to Makefile that makes it easy to create
68        "pcre.dll" under mingw when using Configure/Make. I added stuff to
69        Makefile.am that cause it to include this special target, without
70        affecting anything else. Note that the same mingw target plus all
71        the other distribution libraries and programs are now supported
72        when configuring with CMake (see 6 below) instead of with
73        Configure/Make.
75    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
76        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
77        exported in the Windows port". It has not yet been confirmed that the patch
78        solves the problem, but it does no harm.
80    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
81        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
82        with CMake, and also correct the comment about stack recursion.
84    7.  Remove the automatic building of pcredemo from the ./configure system and
85        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
86        of a program that users should build themselves after PCRE is installed, so
87        building it automatically is not really right. What is more, it gave
88        trouble in some build environments.
90    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
93    Version 7.5 10-Jan-08
94    ---------------------
96    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
97        values in parens when parsing an RE using the C++ wrapper."
99    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
100        Characters greater than 255 were excluded from the class instead of being
101        included.
103    3.  The same bug as (2) above applied to negated POSIX classes such as
104        [:^space:].
106    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
107        defined or documented. It seems to have been a typo for PCRE_STATIC, so
108        I have changed it.
110    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
111        first named subpattern) and a construct such as (?&a) would reference the
112        first named subpattern whose name started with "a" (in other words, the
113        length check was missing). Both these problems are fixed. "Subpattern name
114        expected" is now given for (?&) (a zero-length name), and this patch also
115        makes it give the same error for \k'' (previously it complained that that
116        was a reference to a non-existent subpattern).
118    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
119        this is right because (?- can be followed by option settings as well as by
120        digits. I have, however, made the messages clearer.
122    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
123        than the number used in the conditional) now cause a compile-time error.
124        This is actually not compatible with Perl, which accepts such patterns, but
125        treats the conditional as always being FALSE (as PCRE used to), but it
126        seems to me that giving a diagnostic is better.
128    8.  Change "alphameric" to the more common word "alphanumeric" in comments
129        and messages.
131    9.  Fix two occurrences of "backslash" in comments that should have been
132        "backspace".
134    10. Remove two redundant lines of code that can never be obeyed (their function
135        was moved elsewhere).
137    11. The program that makes PCRE's Unicode character property table had a bug
138        which caused it to generate incorrect table entries for sequences of
139        characters that have the same character type, but are in different scripts.
140        It amalgamated them into a single range, with the script of the first of
141        them. In other words, some characters were in the wrong script. There were
142        thirteen such cases, affecting characters in the following ranges:
144          U+002b0 - U+002c1
145          U+0060c - U+0060d
146          U+0061e - U+00612
147          U+0064b - U+0065e
148          U+0074d - U+0076d
149          U+01800 - U+01805
150          U+01d00 - U+01d77
151          U+01d9b - U+01dbf
152          U+0200b - U+0200f
153          U+030fc - U+030fe
154          U+03260 - U+0327f
155          U+0fb46 - U+0fbb1
156          U+10450 - U+1049d
158    12. The -o option (show only the matching part of a line) for pcregrep was not
159        compatible with GNU grep in that, if there was more than one match in a
160        line, it showed only the first of them. It now behaves in the same way as
161        GNU grep.
163    13. If the -o and -v options were combined for pcregrep, it printed a blank
164        line for every non-matching line. GNU grep prints nothing, and pcregrep now
165        does the same. The return code can be used to tell if there were any
166        non-matching lines.
168    14. Added --file-offsets and --line-offsets to pcregrep.
170    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
171        infinitely looping recursion. The bug was that positive lookaheads were not
172        being skipped when checking for a possible empty match (negative lookaheads
173        and both kinds of lookbehind were skipped).
175    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
176        inclusion of <windows.h> to before rather than after the definition of
177        INVALID_FILE_ATTRIBUTES (patch from David Byron).
179    17. Specifying a possessive quantifier with a specific limit for a Unicode
180        character property caused pcre_compile() to compile bad code, which led at
181        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
182        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
183        caused the error; without that there was no problem.
185    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
187    19. Added --enable-pcretest-libreadline.
189    20. In pcrecpp.cc, the variable 'count' was incremented twice in
190        RE::GlobalReplace(). As a result, the number of replacements returned was
191        double what it should be. I removed one of the increments, but Craig sent a
192        later patch that removed the other one (the right fix) and added unit tests
193        that check the return values (which was not done before).
195    21. Several CMake things:
197        (1) Arranged that, when cmake is used on Unix, the libraries end up with
198            the names libpcre and libpcreposix, not just pcre and pcreposix.
200        (2) The above change means that pcretest and pcregrep are now correctly
201            linked with the newly-built libraries, not previously installed ones.
205    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
206        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
207        UTF-8 newline character). The key issue is that the pattern starts .*;
208        this means that the match must be either at the beginning, or after a
209        newline. The bug was in the code for advancing after a failed match and
210        checking that the new position followed a newline. It was not taking
211        account of UTF-8 characters correctly.
213    23. PCRE was behaving differently from Perl in the way it recognized POSIX
214        character classes. PCRE was not treating the sequence [:...:] as a
215        character class unless the ... were all letters. Perl, however, seems to
216        allow any characters between [: and :], though of course it rejects as
217        unknown any "names" that contain non-letters, because all the known class
218        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
219        for example, whereas PCRE did not - it did not recognize a POSIX character
220        class. This seemed a bit dangerous, so the code has been changed to be
221        closer to Perl. The behaviour is not identical to Perl, because PCRE will
222        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
223        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
224        Perl does, and where it didn't before.
226    24. Rewrite so as to remove the single use of %n from pcregrep because in some
227        Windows environments %n is disabled by default.
230    Version 7.4 21-Sep-07
231    ---------------------
233    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
234        means that a class such as [\s] counted as "explicit reference to CR or
235        LF". That isn't really right - the whole point of the change was to try to
236        help when there was an actual mention of one of the two characters. So now
237        the change happens only if \r or \n (or a literal CR or LF) character is
238        encountered.
240    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
241        of both had grown to the point where there were only 3 bits left.
242        Fortunately, there was spare space in the data structure, and so I have
243        moved the internal flags into a new 16-bit field to free up more option
244        bits.
246    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
247        but did not set the internal JCHANGED flag - either of these is enough to
248        control the way the "get" function works - but the PCRE_INFO_JCHANGED
249        facility is supposed to tell if (?J) was ever used, so now (?J) at the
250        start sets both bits.
252    4.  Added options (at build time, compile time, exec time) to change \R from
253        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
255    5.  doc/pcresyntax.html was missing from the distribution.
257    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
258        compatibility, even though it is no longer used.
260    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
261        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
262        windows.h file is present (where different names are used). [This was
263        reversed later after testing - see 16 below.]
265    8.  Changed all #include <config.h> to #include "config.h". There were also
266        some further <pcre.h> cases that I changed to "pcre.h".
268    9.  When pcregrep was used with the --colour option, it missed the line ending
269        sequence off the lines that it output.
271    10. It was pointed out to me that arrays of string pointers cause lots of
272        relocations when a shared library is dynamically loaded. A technique of
273        using a single long string with a table of offsets can drastically reduce
274        these. I have refactored PCRE in four places to do this. The result is
275        dramatic:
277          Originally:                          290
278          After changing UCP table:            187
279          After changing error message table:   43
280          After changing table of "verbs"       36
281          After changing table of Posix names   22
283        Thanks to the folks working on Gregex for glib for this insight.
285    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
286        unicode-properties was also set.
288    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
290    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
291        checked only for CRLF.
293    14. Added casts to pcretest.c to avoid compiler warnings.
295    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
297    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
298        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
299        entirely. This removes changes made in 7 above.
301    17. The CMake files have been updated, and there is now more information about
302        building with CMake in the NON-UNIX-USE document.
305    Version 7.3 28-Aug-07
306    ---------------------
308     1. In the rejigging of the build system that eventually resulted in 7.1, the
309        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
310        brackets there is not right, since it causes compilers to look for an
311        installed pcre.h, not the version that is in the source that is being
312        compiled (which of course may be different). I have changed it back to:
314          #include "pcre.h"
316        I have a vague recollection that the change was concerned with compiling in
317        different directories, but in the new build system, that is taken care of
318        by the VPATH setting the Makefile.
320     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
321        when the subject happened to end in the byte 0x85 (e.g. if the last
322        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
323        characters but of course it shouldn't be taken as a newline when it is part
324        of another character. The bug was that, for an unlimited repeat of . in
325        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
326        characters when looking for a newline.
328     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
330     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
331        in debug output.
333     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
334        long printing in the pcrecpp unittest when running under MinGW.
336     6. ESC_K was left out of the EBCDIC table.
338     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
339        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
340        limit also applies to "virtual nesting" when a pattern is recursive, and in
341        this case 1000 isn't so big. I have been able to remove this limit at the
342        expense of backing off one optimization in certain circumstances. Normally,
343        when pcre_exec() would call its internal match() function recursively and
344        immediately return the result unconditionally, it uses a "tail recursion"
345        feature to save stack. However, when a subpattern that can match an empty
346        string has an unlimited repetition quantifier, it no longer makes this
347        optimization. That gives it a stack frame in which to save the data for
348        checking that an empty string has been matched. Previously this was taken
349        from the 1000-entry workspace that had been reserved. So now there is no
350        explicit limit, but more stack is used.
352     8. Applied Daniel's patches to solve problems with the import/export magic
353        syntax that is required for Windows, and which was going wrong for the
354        pcreposix and pcrecpp parts of the library. These were overlooked when this
355        problem was solved for the main library.
357     9. There were some crude static tests to avoid integer overflow when computing
358        the size of patterns that contain repeated groups with explicit upper
359        limits. As the maximum quantifier is 65535, the maximum group length was
360        set at 30,000 so that the product of these two numbers did not overflow a
361        32-bit integer. However, it turns out that people want to use groups that
362        are longer than 30,000 bytes (though not repeat them that many times).
363        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
364        made it possible to implement the integer overflow checks in a much more
365        dynamic way, which I have now done. The artificial limitation on group
366        length has been removed - we now have only the limit on the total length of
367        the compiled pattern, which depends on the LINK_SIZE setting.
369    10. Fixed a bug in the documentation for get/copy named substring when
370        duplicate names are permitted. If none of the named substrings are set, the
371        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
372        empty string.
374    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
375        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
376        because the ] is interpreted as the first data character and the
377        terminating ] is not found. PCRE has been made compatible with Perl in this
378        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
379        cause memory overwriting.
381    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
382        string has been matched (to stop an infinite loop). It was not recognizing
383        a conditional subpattern that could match an empty string if that
384        subpattern was within another subpattern. For example, it looped when
385        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
386        condition was not nested. This bug has been fixed.
388    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
389        past the start of the subject in the presence of bytes with the top bit
390        set, for example "\x8aBCD".
392    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
393        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
395    14. Optimized (?!) to (*FAIL).
397    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
398        This restricts code points to be within the range 0 to 0x10FFFF, excluding
399        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
400        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
401        does: it's just the validity check that is more restrictive.
403    16. Inserted checks for integer overflows during escape sequence (backslash)
404        processing, and also fixed erroneous offset values for syntax errors during
405        backslash processing.
407    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
408        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
410    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
411        caused an overrun.
413    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
414        something other than just ASCII characters) inside a group that had an
415        unlimited repeat caused a loop at compile time (while checking to see
416        whether the group could match an empty string).
418    20. Debugging a pattern containing \p or \P could cause a crash. For example,
419        [\P{Any}] did so. (Error in the code for printing property names.)
421    21. An orphan \E inside a character class could cause a crash.
423    22. A repeated capturing bracket such as (A)? could cause a wild memory
424        reference during compilation.
426    23. There are several functions in pcre_compile() that scan along a compiled
427        expression for various reasons (e.g. to see if it's fixed length for look
428        behind). There were bugs in these functions when a repeated \p or \P was
429        present in the pattern. These operators have additional parameters compared
430        with \d, etc, and these were not being taken into account when moving along
431        the compiled data. Specifically:
433        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
434            length.
436        (b) An item such as \pL+ within a repeated group could cause crashes or
437            loops.
439        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
440            "reference to non-existent subpattern" error.
442        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
444    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
445        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
447    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
449    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
450        character were causing crashes (broken optimization).
452    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
453        \p or \P) caused a compile-time loop.
455    28. More problems have arisen in unanchored patterns when CRLF is a valid line
456        break. For example, the unstudied pattern [\r\n]A does not match the string
457        "\r\nA" because change 7.0/46 below moves the current point on by two
458        characters after failing to match at the start. However, the pattern \nA
459        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
460        the same is true. There doesn't seem any very clean way out of this, but
461        what I have chosen to do makes the common cases work: PCRE now takes note
462        of whether there can be an explicit match for \r or \n anywhere in the
463        pattern, and if so, 7.0/46 no longer applies. As part of this change,
464        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
465        pattern has explicit CR or LF references.
467    29. Added (*CR) etc for changing newline setting at start of pattern.
470    Version 7.2 19-Jun-07
471    ---------------------
473     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
474        which is apparently normally available under Windows.
476     2. Re-jig the pcregrep tests with different newline settings in an attempt
477        to make them independent of the local environment's newline setting.
479     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
481     4. Some of the "internals" tests were previously cut out when the link size
482        was not 2, because the output contained actual offsets. The recent new
483        "Z" feature of pcretest means that these can be cut out, making the tests
484        usable with all link sizes.
486     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
487        stack recursion. This gives a massive performance boost under BSD, but just
488        a small improvement under Linux. However, it saves one field in the frame
489        in all cases.
491     6. Added more features from the forthcoming Perl 5.10:
493        (a) (?-n) (where n is a string of digits) is a relative subroutine or
494            recursion call. It refers to the nth most recently opened parentheses.
496        (b) (?+n) is also a relative subroutine call; it refers to the nth next
497            to be opened parentheses.
499        (c) Conditions that refer to capturing parentheses can be specified
500            relatively, for example, (?(-2)... or (?(+3)...
502        (d) \K resets the start of the current match so that everything before
503            is not part of it.
505        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
507        (f) \g{name} is another synonym - part of Perl 5.10's unification of
508            reference syntax.
510        (g) (?| introduces a group in which the numbering of parentheses in each
511            alternative starts with the same number.
513        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
515     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
518     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
519        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
520        for detecting groups that can match an empty string.
522     9. A pattern with a very large number of alternatives (more than several
523        hundred) was running out of internal workspace during the pre-compile
524        phase, where pcre_compile() figures out how much memory will be needed. A
525        bit of new cunning has reduced the workspace needed for groups with
526        alternatives. The 1000-alternative test pattern now uses 12 bytes of
527        workspace instead of running out of the 4096 that are available.
529    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
531    11. Applied patch from Google to remove an optimization that didn't quite work.
532        The report of the bug said:
534          pcrecpp::RE("a*").FullMatch("aaa") matches, while
535          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
536          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
538    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
539        it matched the wrong number of bytes.
542    Version 7.1 24-Apr-07
543  ---------------------  ---------------------
545   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 136  Version 7.1 12-Mar-07 Line 674  Version 7.1 12-Mar-07
674      string at the end of a line did not allow for this case. They now check for      string at the end of a line did not allow for this case. They now check for
675      it specially.      it specially.
677    20. pcretest is supposed to handle patterns and data of any length, by
678        extending its buffers when necessary. It was getting this wrong when the
679        buffer for a data line had to be extended.
681    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
682        CRLF as a newline sequence.
684    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
685        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
686        I have nevertheless tidied it up.
688    23. Added some casts to kill warnings from HP-UX ia64 compiler.
690    24. Added a man page for pcre-config.
693  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
694  ---------------------  ---------------------

Removed from v.143  
changed lines
  Added in v.329

  ViewVC Help
Powered by ViewVC 1.1.5