[BACK]Return to README CVS log [TXT] [DIR] Up to [parser3project] / win32 / pcre

Diff for /win32/pcre/README between versions 1.1 and 1.3

version 1.1, 2008/08/15 14:53:20 version 1.3, 2009/04/21 10:23:57
Line 1 Line 1
 README file for PCRE (Perl-compatible regular expression library)  README file for PCRE (Perl-compatible regular expression library)
 -----------------------------------------------------------------  -----------------------------------------------------------------
   
 The latest release of PCRE is always available from  The latest release of PCRE is always available in three alternative formats
   from:
   
   ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
     ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.bz2
     ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.zip
   
 There is a mailing list for discussion about the development of PCRE at  There is a mailing list for discussion about the development of PCRE at
   
Line 82  documentation is supplied in two other f Line 85  documentation is supplied in two other f
      in various ways, and rooted in a file called index.html, is distributed in       in various ways, and rooted in a file called index.html, is distributed in
      doc/html and installed in <prefix>/share/doc/pcre/html.       doc/html and installed in <prefix>/share/doc/pcre/html.
   
   Users of PCRE have contributed files containing the documentation for various
   releases in CHM format. These can be found in the Contrib directory of the FTP
   site (see next section).
   
   
 Contributions by users of PCRE  Contributions by users of PCRE
 ------------------------------  ------------------------------
Line 158  library. You can read more about them in Line 165  library. You can read more about them in
   it will try to find a C++ compiler and C++ header files, and if it succeeds,    it will try to find a C++ compiler and C++ header files, and if it succeeds,
   it will try to build the C++ wrapper.    it will try to build the C++ wrapper.
   
 . If you want to make use of the support for UTF-8 character strings in PCRE,  . If you want to make use of the support for UTF-8 Unicode character strings in
   you must add --enable-utf8 to the "configure" command. Without it, the code    PCRE, you must add --enable-utf8 to the "configure" command. Without it, the
   for handling UTF-8 is not included in the library. (Even when included, it    code for handling UTF-8 is not included in the library. Even when included,
   still has to be enabled by an option at run time.)    it still has to be enabled by an option at run time. When PCRE is compiled
     with this option, its input can only either be ASCII or UTF-8, even when
     running on EBCDIC platforms. It is not possible to use both --enable-utf8 and
     --enable-ebcdic at the same time.
   
 . If, in addition to support for UTF-8 character strings, you want to include  . If, in addition to support for UTF-8 character strings, you want to include
   support for the \P, \p, and \X sequences that recognize Unicode character    support for the \P, \p, and \X sequences that recognize Unicode character
Line 252  library. You can read more about them in Line 262  library. You can read more about them in
   pcre_chartables.c.dist. See "Character tables" below for further information.    pcre_chartables.c.dist. See "Character tables" below for further information.
   
 . It is possible to compile PCRE for use on systems that use EBCDIC as their  . It is possible to compile PCRE for use on systems that use EBCDIC as their
   default character code (as opposed to ASCII) by specifying    character code (as opposed to ASCII) by specifying
   
   --enable-ebcdic    --enable-ebcdic
   
   This automatically implies --enable-rebuild-chartables (see above).    This automatically implies --enable-rebuild-chartables (see above). However,
     when PCRE is built this way, it always operates in EBCDIC. It cannot support
     both EBCDIC and UTF-8.
   
 . It is possible to compile pcregrep to use libz and/or libbz2, in order to  . It is possible to compile pcregrep to use libz and/or libbz2, in order to
   read .gz and .bz2 files (respectively), by specifying one or both of    read .gz and .bz2 files (respectively), by specifying one or both of
Line 283  library. You can read more about them in Line 295  library. You can read more about them in
   to specify something like LIBS="-lncurses" as well. This is because, to quote    to specify something like LIBS="-lncurses" as well. This is because, to quote
   the readline INSTALL, "Readline uses the termcap functions, but does not link    the readline INSTALL, "Readline uses the termcap functions, but does not link
   with the termcap or curses library itself, allowing applications which link    with the termcap or curses library itself, allowing applications which link
   with readline the to choose an appropriate library."    with readline the to choose an appropriate library." If you get error
     messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,
     this is the problem, and linking with the ncurses library should fix it.
   
 The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
   
Line 640  The distribution should contain the foll Line 654  The distribution should contain the foll
   pcre_study.c            )    pcre_study.c            )
   pcre_tables.c           )    pcre_tables.c           )
   pcre_try_flipped.c      )    pcre_try_flipped.c      )
   pcre_ucp_searchfuncs.c  )    pcre_ucd.c              )
   pcre_valid_utf8.c       )    pcre_valid_utf8.c       )
   pcre_version.c          )    pcre_version.c          )
   pcre_xclass.c           )    pcre_xclass.c           )
Line 649  The distribution should contain the foll Line 663  The distribution should contain the foll
   pcre.h.in               template for pcre.h when built by "configure"    pcre.h.in               template for pcre.h when built by "configure"
   pcreposix.h             header for the external POSIX wrapper API    pcreposix.h             header for the external POSIX wrapper API
   pcre_internal.h         header for internal use    pcre_internal.h         header for internal use
   ucp.h                   ) headers concerned with    ucp.h                   header for Unicode property handling
   ucpinternal.h           )   Unicode property handling  
   ucptable.h              ) (this one is the data table)  
   
   config.h.in             template for config.h, which is built by "configure"    config.h.in             template for config.h, which is built by "configure"
   
Line 725  The distribution should contain the foll Line 737  The distribution should contain the foll
   
 (D) Auxiliary files for cmake support  (D) Auxiliary files for cmake support
   
     cmake/COPYING-CMAKE-SCRIPTS
     cmake/FindPackageHandleStandardArgs.cmake
     cmake/FindReadline.cmake
   CMakeLists.txt    CMakeLists.txt
   config-cmake.h.in    config-cmake.h.in
   
Line 749  The distribution should contain the foll Line 764  The distribution should contain the foll
 Philip Hazel  Philip Hazel
 Email local part: ph10  Email local part: ph10
 Email domain: cam.ac.uk  Email domain: cam.ac.uk
 Last updated: 13 April 2008  Last updated: 21 March 2009
Removed from v.1.1  
changed lines
  Added in v.1.3

E-mail: