ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 240 by ph10, Tue Sep 11 15:47:20 2007 UTC revision 405 by ph10, Mon Mar 23 12:05:20 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.4 10-Sep-07  Version 7.9 xx-xxx-09
5    ---------------------
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
45    9.  If auto-callout was enabled in a pattern with a conditional group whose
46        condition was an assertion, PCRE could crash during matching, both with
47        pcre_exec() and pcre_dfa_exec().
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
55    12. Added the -M command line option to pcretest.
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
64    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
65        from Martin Jerabek that uses macro names for all relevant character and
66        string constants.
68    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
69        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
70        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
71        these, but not everybody uses configure.
73    19. A conditional group that had only one branch was not being correctly
74        recognized as an item that could match an empty string. This meant that an
75        enclosing group might also not be so recognized, causing infinite looping
76        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
77        with the subject "ab", where knowledge that the repeated group can match
78        nothing is needed in order to break the loop.
80    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
81        exec(), but without supplying a callout function, matching went wrong.
83    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
84        leak if the size of the offset vector was greater than 30. When the vector
85        is smaller, the saved offsets during recursion go onto a local stack
86        vector, but for larger vectors malloc() is used. It was failing to free
87        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
88        error, in fact).
90    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
91        heapframe that is used only when UTF-8 support is enabled. This caused no
92        problem, but was untidy.
94    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
95        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
96        included within another project.
100    Version 7.8 05-Sep-08
101    ---------------------
103    1.  Replaced UCP searching code with optimized version as implemented for Ad
104        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
105        stage table and inline lookup instead of a function, giving speed ups of 2
106        to 5 times on some simple patterns that I tested. Permission was given to
107        distribute the MultiStage2.py script that generates the tables (it's not in
108        the tarball, but is in the Subversion repository).
110    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
111        scripts.
113    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
114        a group with a zero qualifier. The result of the study could be incorrect,
115        or the function might crash, depending on the pattern.
117    4.  Caseless matching was not working for non-ASCII characters in back
118        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
119        It now works when Unicode Property Support is available.
121    5.  In pcretest, an escape such as \x{de} in the data was always generating
122        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
123        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
124        truncation.
126    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
128    7.  Added two (int) casts to pcregrep when printing the difference of two
129        pointers, in case they are 64-bit values.
131    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
132        test 2 if it fails.
134    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
135        and a #define of that name to empty if it is not externally set. This is to
136        allow users of MSVC to set it if necessary.
138    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
139        the convenience functions in the pcre_get.c source file.
141    11. An option change at the start of a pattern that had top-level alternatives
142        could cause overwriting and/or a crash. This command provoked a crash in
143        some environments:
145          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
147        This potential security problem was recorded as CVE-2008-2371.
149    12. For a pattern where the match had to start at the beginning or immediately
150        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
151        pcre_dfa_exec() could read past the end of the passed subject if there was
152        no match. To help with detecting such bugs (e.g. with valgrind), I modified
153        pcretest so that it places the subject at the end of its malloc-ed buffer.
155    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
156        exec() might read past the end of the data buffer in UTF-8 mode.
158    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
159        the data contained the byte 0x85 as part of a UTF-8 character within its
160        first line. This applied both to normal and DFA matching.
162    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
163        /^[^d]*?$/8 failed to match "abc".
165    16. Added a missing copyright notice to pcrecpp_internal.h.
167    17. Make it more clear in the documentation that values returned from
168        pcre_exec() in ovector are byte offsets, not character counts.
170    18. Tidied a few places to stop certain compilers from issuing warnings.
172    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
173        supplied by Stefan Weber. I made a further small update for 7.8 because
174        there is a change of source arrangements: the pcre_searchfuncs.c module is
175        replaced by pcre_ucd.c.
178    Version 7.7 07-May-08
179    ---------------------
181    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
182        a string to a long long, pretend we don't even have a long long." This is
183        done by checking for the strtoq, strtoll, and _strtoi64 functions.
185    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
186        pre-7.6 versions, which defined a global no_arg variable instead of putting
187        it in the RE class. (See also #8 below.)
189    3.  Remove a line of dead code, identified by coverity and reported by Nuno
190        Lopes.
192    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
194        (1) The include/exclude patterns were being applied to the whole pathnames
195            of files, instead of just to the final components.
197        (2) If there was more than one level of directory, the subdirectories were
198            skipped unless they satisfied the include/exclude conditions. This is
199            inconsistent with GNU grep (and could even be seen as contrary to the
200            pcregrep specification - which I improved to make it absolutely clear).
201            The action now is always to scan all levels of directory, and just
202            apply the include/exclude patterns to regular files.
204    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
205        --exclude_dir in the tests to avoid scanning .svn directories.
207    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
208        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
209        doesn't support NULs in patterns.
211    7.  Added some missing "const"s to declarations of static tables in
212        pcre_compile.c and pcre_dfa_exec.c.
214    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
215        caused by fix #2  above. (Subsequently also a second patch to fix the
216        first patch. And a third patch - this was a messy problem.)
218    9.  Applied Craig's patch to remove the use of push_back().
220    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
221        matching function regexec().
223    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
224        which, however, unlike Perl's \g{...}, are subroutine calls, not back
225        references. PCRE supports relative numbers with this syntax (I don't think
226        Oniguruma does).
228    12. Previously, a group with a zero repeat such as (...){0} was completely
229        omitted from the compiled regex. However, this means that if the group
230        was called as a subroutine from elsewhere in the pattern, things went wrong
231        (an internal error was given). Such groups are now left in the compiled
232        pattern, with a new opcode that causes them to be skipped at execution
233        time.
235    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
236        to the way PCRE behaves:
238        (a) A lone ] character is dis-allowed (Perl treats it as data).
240        (b) A back reference to an unmatched subpattern matches an empty string
241            (Perl fails the current match path).
243        (c) A data ] in a character class must be notated as \] because if the
244            first data character in a class is ], it defines an empty class. (In
245            Perl it is not possible to have an empty class.) The empty class []
246            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
247            The negative empty class [^] matches any one character, independently
248            of the DOTALL setting.
250    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
251        non-existent subpattern following a character class starting with ']' and
252        containing () gave an internal compiling error instead of "reference to
253        non-existent subpattern". Fortunately, when the pattern did exist, the
254        compiled code was correct. (When scanning forwards to check for the
255        existencd of the subpattern, it was treating the data ']' as terminating
256        the class, so got the count wrong. When actually compiling, the reference
257        was subsequently set up correctly.)
259    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
260        it was being rejected as not supported by pcre_dfa_exec(), even though
261        other assertions are supported. I have made pcre_dfa_exec() support
262        (*FAIL).
264    16. The implementation of 13c above involved the invention of a new opcode,
265        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
266        cannot be changed at match time, I realized I could make a small
267        improvement to matching performance by compiling OP_ALLANY instead of
268        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
269        on the OP_ANY path.
271    17. Compiling pcretest on Windows with readline support failed without the
272        following two fixes: (1) Make the unistd.h include conditional on
273        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
275    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
276        ncurses library to be included for pcretest when ReadLine support is
277        requested, but also to allow for it to be overridden. This patch came from
278        Daniel Bergström.
280    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
281        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
282        any errors with the current Unicode tables. Thanks to Peter Kankowski for
283        spotting this.
286    Version 7.6 28-Jan-08
287    ---------------------
289    1.  A character class containing a very large number of characters with
290        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
291        overflow.
293    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
294        HAVE_LONG_LONG is not defined.
296    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
297        bring them up to date and include new features. This patch includes:
299        - Fixed PH's badly added libz and libbz2 support.
300        - Fixed a problem with static linking.
301        - Added pcredemo. [But later removed - see 7 below.]
302        - Fixed dftables problem and added an option.
303        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
304            HAVE_LONG_LONG.
305        - Added readline support for pcretest.
306        - Added an listing of the option settings after cmake has run.
308    4.  A user submitted a patch to Makefile that makes it easy to create
309        "pcre.dll" under mingw when using Configure/Make. I added stuff to
310        Makefile.am that cause it to include this special target, without
311        affecting anything else. Note that the same mingw target plus all
312        the other distribution libraries and programs are now supported
313        when configuring with CMake (see 6 below) instead of with
314        Configure/Make.
316    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
317        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
318        exported in the Windows port". It has not yet been confirmed that the patch
319        solves the problem, but it does no harm.
321    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
322        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
323        with CMake, and also correct the comment about stack recursion.
325    7.  Remove the automatic building of pcredemo from the ./configure system and
326        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
327        of a program that users should build themselves after PCRE is installed, so
328        building it automatically is not really right. What is more, it gave
329        trouble in some build environments.
331    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
334    Version 7.5 10-Jan-08
335    ---------------------
337    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
338        values in parens when parsing an RE using the C++ wrapper."
340    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
341        Characters greater than 255 were excluded from the class instead of being
342        included.
344    3.  The same bug as (2) above applied to negated POSIX classes such as
345        [:^space:].
347    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
348        defined or documented. It seems to have been a typo for PCRE_STATIC, so
349        I have changed it.
351    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
352        first named subpattern) and a construct such as (?&a) would reference the
353        first named subpattern whose name started with "a" (in other words, the
354        length check was missing). Both these problems are fixed. "Subpattern name
355        expected" is now given for (?&) (a zero-length name), and this patch also
356        makes it give the same error for \k'' (previously it complained that that
357        was a reference to a non-existent subpattern).
359    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
360        this is right because (?- can be followed by option settings as well as by
361        digits. I have, however, made the messages clearer.
363    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
364        than the number used in the conditional) now cause a compile-time error.
365        This is actually not compatible with Perl, which accepts such patterns, but
366        treats the conditional as always being FALSE (as PCRE used to), but it
367        seems to me that giving a diagnostic is better.
369    8.  Change "alphameric" to the more common word "alphanumeric" in comments
370        and messages.
372    9.  Fix two occurrences of "backslash" in comments that should have been
373        "backspace".
375    10. Remove two redundant lines of code that can never be obeyed (their function
376        was moved elsewhere).
378    11. The program that makes PCRE's Unicode character property table had a bug
379        which caused it to generate incorrect table entries for sequences of
380        characters that have the same character type, but are in different scripts.
381        It amalgamated them into a single range, with the script of the first of
382        them. In other words, some characters were in the wrong script. There were
383        thirteen such cases, affecting characters in the following ranges:
385          U+002b0 - U+002c1
386          U+0060c - U+0060d
387          U+0061e - U+00612
388          U+0064b - U+0065e
389          U+0074d - U+0076d
390          U+01800 - U+01805
391          U+01d00 - U+01d77
392          U+01d9b - U+01dbf
393          U+0200b - U+0200f
394          U+030fc - U+030fe
395          U+03260 - U+0327f
396          U+0fb46 - U+0fbb1
397          U+10450 - U+1049d
399    12. The -o option (show only the matching part of a line) for pcregrep was not
400        compatible with GNU grep in that, if there was more than one match in a
401        line, it showed only the first of them. It now behaves in the same way as
402        GNU grep.
404    13. If the -o and -v options were combined for pcregrep, it printed a blank
405        line for every non-matching line. GNU grep prints nothing, and pcregrep now
406        does the same. The return code can be used to tell if there were any
407        non-matching lines.
409    14. Added --file-offsets and --line-offsets to pcregrep.
411    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
412        infinitely looping recursion. The bug was that positive lookaheads were not
413        being skipped when checking for a possible empty match (negative lookaheads
414        and both kinds of lookbehind were skipped).
416    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
417        inclusion of <windows.h> to before rather than after the definition of
418        INVALID_FILE_ATTRIBUTES (patch from David Byron).
420    17. Specifying a possessive quantifier with a specific limit for a Unicode
421        character property caused pcre_compile() to compile bad code, which led at
422        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
423        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
424        caused the error; without that there was no problem.
426    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
428    19. Added --enable-pcretest-libreadline.
430    20. In pcrecpp.cc, the variable 'count' was incremented twice in
431        RE::GlobalReplace(). As a result, the number of replacements returned was
432        double what it should be. I removed one of the increments, but Craig sent a
433        later patch that removed the other one (the right fix) and added unit tests
434        that check the return values (which was not done before).
436    21. Several CMake things:
438        (1) Arranged that, when cmake is used on Unix, the libraries end up with
439            the names libpcre and libpcreposix, not just pcre and pcreposix.
441        (2) The above change means that pcretest and pcregrep are now correctly
442            linked with the newly-built libraries, not previously installed ones.
446    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
447        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
448        UTF-8 newline character). The key issue is that the pattern starts .*;
449        this means that the match must be either at the beginning, or after a
450        newline. The bug was in the code for advancing after a failed match and
451        checking that the new position followed a newline. It was not taking
452        account of UTF-8 characters correctly.
454    23. PCRE was behaving differently from Perl in the way it recognized POSIX
455        character classes. PCRE was not treating the sequence [:...:] as a
456        character class unless the ... were all letters. Perl, however, seems to
457        allow any characters between [: and :], though of course it rejects as
458        unknown any "names" that contain non-letters, because all the known class
459        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
460        for example, whereas PCRE did not - it did not recognize a POSIX character
461        class. This seemed a bit dangerous, so the code has been changed to be
462        closer to Perl. The behaviour is not identical to Perl, because PCRE will
463        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
464        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
465        Perl does, and where it didn't before.
467    24. Rewrite so as to remove the single use of %n from pcregrep because in some
468        Windows environments %n is disabled by default.
471    Version 7.4 21-Sep-07
472  ---------------------  ---------------------
474  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
# Line 25  Version 7.4 10-Sep-07 Line 492  Version 7.4 10-Sep-07
493  4.  Added options (at build time, compile time, exec time) to change \R from  4.  Added options (at build time, compile time, exec time) to change \R from
494      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.      matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
 5.  doc/pcresyntax.html was missing from the distribution.  
496  6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward  5.  doc/pcresyntax.html was missing from the distribution.
498    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
499      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
501  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
502      strtoull to pcrecpp.cc to select the available functions in WIN32 (where      strtoull to pcrecpp.cc to select the available functions in WIN32 when the
503      different names are used).      windows.h file is present (where different names are used). [This was
504        reversed later after testing - see 16 below.]
505  8.  Changed all #include <config.h> to #include "config.h". There were also  
506    8.  Changed all #include <config.h> to #include "config.h". There were also
507      some further <pcre.h> cases that I changed to "pcre.h".      some further <pcre.h> cases that I changed to "pcre.h".
509  9.  When pcregrep was used with the --colour option, it missed the line ending  9.  When pcregrep was used with the --colour option, it missed the line ending
510      sequence off the lines that it output.      sequence off the lines that it output.
512  10. It was pointed out to me that arrays of string pointers cause lots of  10. It was pointed out to me that arrays of string pointers cause lots of
513      relocations when a shared library is dynamically loaded. A technique of      relocations when a shared library is dynamically loaded. A technique of
514      using a single long string with a table of offsets can drastically reduce      using a single long string with a table of offsets can drastically reduce
515      these. I have refactored PCRE in four places to do this. The result is      these. I have refactored PCRE in four places to do this. The result is
516      dramatic:      dramatic:
518        Originally:                          290        Originally:                          290
519        After changing UCP table:            187        After changing UCP table:            187
520        After changing error message table:   43        After changing error message table:   43
521        After changing table of "verbs"       36        After changing table of "verbs"       36
522        After changing table of Posix names   22        After changing table of Posix names   22
524      Thanks to the folks working on Gregex for glib for this insight.      Thanks to the folks working on Gregex for glib for this insight.
526    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
527        unicode-properties was also set.
529    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
531    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
532        checked only for CRLF.
534    14. Added casts to pcretest.c to avoid compiler warnings.
536    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
538    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
539        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
540        entirely. This removes changes made in 7 above.
542    17. The CMake files have been updated, and there is now more information about
543        building with CMake in the NON-UNIX-USE document.
546  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
547  ---------------------  ---------------------

Removed from v.240  
changed lines
  Added in v.405

  ViewVC Help
Powered by ViewVC 1.1.5