/[pcre]/code/trunk/README

Diff of /code/trunk/README

Parent Directory | Revision Log | View Patch Patch

-revision 127 by ph10,
Mon Mar 19 11:44:45 2007 UTC
+revision 654 by ph10,
Tue Aug  2 11:00:40 2011 UTC
 Line 1
  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.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
-Line 21 
 The contents of this README file are:
+Line 24 
 The contents of this README file are:
    Shared libraries on Unix-like systems
    Cross-compiling on Unix-like systems
    Using HP's ANSI C++ compiler (aCC)
+   Using PCRE from MySQL
    Making new tarballs
    Testing PCRE
    Character tables
-Line 30 
 The contents of this README file are:
+Line 34 
 The contents of this README file are:
  The PCRE APIs
  -------------
- PCRE is written in C, and it has its own API. The distribution now includes a
+ PCRE is written in C, and it has its own API. The distribution also includes a
- set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page
+ set of C++ wrapper functions (see the pcrecpp man page for details), courtesy
- for details).
+ of Google Inc.
- Also included in the distribution are a set of C wrapper functions that are
+ In addition, there is a set of C wrapper functions that are based on the POSIX
- based on the POSIX API. These end up in the library called libpcreposix. Note
+ regular expression API (see the pcreposix man page). These end up in the
- that this just provides a POSIX calling interface to PCRE; the regular
+ library called libpcreposix. Note that this just provides a POSIX calling
- expressions themselves still follow Perl syntax and semantics. The POSIX API is
+ interface to PCRE; the regular expressions themselves still follow Perl syntax
- restricted, and does not give full access to all of PCRE's facilities.
+ and semantics. The POSIX API is restricted, and does not give full access to
+ all of PCRE's facilities.
  The header file for the POSIX-style functions is called pcreposix.h. The
  official POSIX name is regex.h, but I did not want to risk possible problems
-Line 81 
 documentation is supplied in two other f
+Line 86 
 documentation is supplied in two other f
       in various ways, and rooted in a file called index.html, is distributed in
       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
  ------------------------------
-Line 91 
 You can find contributions from PCRE use
+Line 100 
 You can find contributions from PCRE use
  There is a README file giving brief descriptions of what they are. Some are
  complete in themselves; others are pointers to URLs containing relevant files.
- Some of this material is likely to be well out-of-date. In particular, several
+ Some of this material is likely to be well out-of-date. Several of the earlier
- of the contributions provide support for compiling PCRE on various flavours of
+ contributions provided support for compiling PCRE on various flavours of
- Windows (I myself do not use Windows), but nowadays there is more Windows
+ Windows (I myself do not use Windows). Nowadays there is more Windows support
- support in the standard distribution.
+ in the standard distribution, so these contibutions have been archived.
  Building PCRE on non-Unix systems
-Line 102 
 Building PCRE on non-Unix systems
+Line 111 
 Building PCRE on non-Unix systems
  For a non-Unix system, please read the comments in the file NON-UNIX-USE,
  though if your system supports the use of "configure" and "make" you may be
- able to build PCRE in the same way as for Unix-like systems.
+ able to build PCRE in the same way as for Unix-like systems. PCRE can also be
+ configured in many platform environments using the GUI facility provided by
+ CMake's cmake-gui command. This creates Makefiles, solution files, etc.
  PCRE has been compiled on many different operating systems. It should be
  straightforward to build PCRE on any system that has a Standard C compiler and
-Line 115 
 Building PCRE on Unix-like systems
+Line 126 
 Building PCRE on Unix-like systems
  If you are using HP's ANSI C++ compiler (aCC), please see the special note
  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
+ The following instructions assume the use of the widely used "configure, make,
+ make install" process. There is also support for CMake in the PCRE
+ distribution; there are some comments about using CMake in the NON-UNIX-USE
+ file, though it can also be used in Unix-like systems.
  To build PCRE on a Unix-like system, first run the "configure" command from the
  PCRE distribution directory, with your current directory set to the directory
  where you want the files to be created. This command is a standard GNU
-Line 143 
 possible to build it as a C++ library, t
+Line 159 
 possible to build it as a C++ library, t
  does not have any features to support this.
  There are some optional features that can be included or omitted from the PCRE
- library. You can read more about them in the pcrebuild man page.
+ library. They are also documented in the pcrebuild man page.
+ . By default, both shared and static libraries are built. You can change this
+   by adding one of these options to the "configure" command:
+   --disable-shared
+   --disable-static
+   (See also "Shared libraries on Unix-like systems" below.)
  . If you want to suppress the building of the C++ wrapper library, you can add
    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,
-   will try to find a C++ compiler and C++ header files, and if it succeeds, it
+   it will try to find a C++ compiler and C++ header files, and if it succeeds,
-   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
    support for the \P, \p, and \X sequences that recognize Unicode character
-Line 163 
 library. You can read more about them in
+Line 190 
 library. You can read more about them in
    supported.
  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any
-   of the Unicode newline sequences as indicating the end of a line. Whatever
+   of the preceding, or any of the Unicode newline sequences as indicating the
-   you specify at build time is the default; the caller of PCRE can change the
+   end of a line. Whatever you specify at build time is the default; the caller
-   selection at run time. The default newline indicator is a single LF character
+   of PCRE can change the selection at run time. The default newline indicator
-   (the Unix standard). You can specify the default newline indicator by adding
+   is a single LF character (the Unix standard). You can specify the default
-   --newline-is-cr or --newline-is-lf or --newline-is-crlf or --newline-is-any
+   newline indicator by adding --enable-newline-is-cr or --enable-newline-is-lf
-   to the "configure" command, respectively.
+   or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
+   --enable-newline-is-any to the "configure" command, respectively.
-   If you specify --newline-is-cr or --newline-is-crlf, some of the standard
-   tests will fail, because the lines in the test files end with LF. Even if
+   If you specify --enable-newline-is-cr or --enable-newline-is-crlf, some of
-   the files are edited to change the line endings, there are likely to be some
+   the standard tests will fail, because the lines in the test files end with
-   failures. With --newline-is-any, many tests should succeed, but there may be
+   LF. Even if the files are edited to change the line endings, there are likely
-   some failures.
+   to be some failures. With --enable-newline-is-anycrlf or
+   --enable-newline-is-any, many tests should succeed, but there may be some
+   failures.
+ . By default, the sequence \R in a pattern matches any Unicode line ending
+   sequence. This is independent of the option specifying what PCRE considers to
+   be the end of a line (see above). However, the caller of PCRE can restrict \R
+   to match only CR, LF, or CRLF. You can make this the default by adding
+   --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
  . When called via the POSIX interface, PCRE uses malloc() to get additional
    storage for processing capturing parentheses if there are more than 10 of
-   them. You can increase this threshold by setting, for example,
+   them in a pattern. You can increase this threshold by setting, for example,
    --with-posix-malloc-threshold=20
-Line 207 
 library. You can read more about them in
+Line 242 
 library. You can read more about them in
  . The default maximum compiled pattern size is around 64K. You can increase
    this by adding --with-link-size=3 to the "configure" command. You can
    increase it even more by setting --with-link-size=4, but this is unlikely
-   ever to be necessary.
+   ever to be necessary. Increasing the internal link size will reduce
+   performance.
  . You can build PCRE so that its internal match() function that is called from
    pcre_exec() does not call itself recursively. Instead, it uses memory blocks
-Line 223 
 library. You can read more about them in
+Line 259 
 library. You can read more about them in
    use deeply nested recursion. There is a discussion about stack sizes in the
    pcrestack man page.
+ . For speed, PCRE uses four tables for manipulating and identifying characters
+   whose code point values are less than 256. By default, it uses a set of
+   tables for ASCII encoding that is part of the distribution. If you specify
+   --enable-rebuild-chartables
+   a program called dftables is compiled and run in the default C locale when
+   you obey "make". It builds a source file called pcre_chartables.c. If you do
+   not specify this option, pcre_chartables.c is created as a copy of
+   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
+   character code (as opposed to ASCII) by specifying
+   --enable-ebcdic
+   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
+   read .gz and .bz2 files (respectively), by specifying one or both of
+   --enable-pcregrep-libz
+   --enable-pcregrep-libbz2
+   Of course, the relevant libraries must be installed on your system.
+ . The default size of internal buffer used by pcregrep can be set by, for
+   example:
+   --with-pcregrep-bufsize=50K
+   The default value is 20K.
+ . It is possible to compile pcretest so that it links with the libreadline
+   library, by specifying
+   --enable-pcretest-libreadline
+   If this is done, when pcretest's input is from a terminal, it reads it using
+   the readline() function. This provides line-editing and history facilities.
+   Note that libreadline is GPL-licenced, so if you distribute a binary of
+   pcretest linked in this way, there may be licensing issues.
+   Setting this option causes the -lreadline option to be added to the pcretest
+   build. In many operating environments with a sytem-installed readline
+   library this is sufficient. However, in some environments (e.g. if an
+   unmodified distribution version of readline is in use), it may be necessary
+   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
+   with the termcap or curses library itself, allowing applications which link
+   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:
  . Makefile is the makefile that builds the library
-Line 234 
 The "configure" script builds the follow
+Line 326 
 The "configure" script builds the follow
  . RunTest is a script for running tests on the basic C library
  . RunGrepTest is a script for running tests on the pcregrep command
- Versions of config.h and pcre.h are distributed in the PCRE tarballs under
+ Versions of config.h and pcre.h are distributed in the PCRE tarballs under the
- the names config.h.generic and pcre.h.generic. These are provided for the
+ names config.h.generic and pcre.h.generic. These are provided for those who
- benefit of those who have to built PCRE without the benefit of "configure". If
+ have to built PCRE without using "configure" or CMake. If you use "configure"
- you use "configure", the .generic versions are not used.
+ or CMake, the .generic versions are not used.
  If a C++ compiler is found, the following files are also built:
-Line 250 
 script that can be run to recreate the c
+Line 342 
 script that can be run to recreate the c
  contains compiler output from tests that "configure" runs.
  Once "configure" has run, you can run "make". It builds two libraries, called
- libpcre and libpcreposix, a test program called pcretest, a demonstration
+ libpcre and libpcreposix, a test program called pcretest, and the pcregrep
- program called pcredemo, and the pcregrep command. If a C++ compiler was found
+ command. If a C++ compiler was found on your system, "make" also builds the C++
- on your system, "make" also builds the C++ wrapper library, which is called
+ wrapper library, which is called libpcrecpp, and some test programs called
- libpcrecpp, and some test programs called pcrecpp_unittest,
+ pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
- pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper
+ Building the C++ wrapper can be disabled by adding --disable-cpp to the
- can be disabled by adding --disable-cpp to the "configure" command.
+ "configure" command.
  The command "make check" runs all the appropriate tests. Details of the PCRE
  tests are given below in a separate section of this document.
-Line 307 
 system. The following are installed (fil
+Line 399 
 system. The following are installed (fil
      pcretest.txt   the pcretest man page
      pcregrep.txt   the pcregrep man page
- Note that the pcredemo program that is built by "configure" is *not* installed
- anywhere. It is a demonstration for programmers wanting to use PCRE.
  If you want to remove PCRE from your system, you can run "make uninstall".
  This removes all the files that "make install" installed. However, it does not
  remove any directories, because these are often shared with other programs.
-Line 371 
 Cross-compiling on Unix-like systems
+Line 460 
 Cross-compiling on Unix-like systems
  ------------------------------------
  You can specify CC and CFLAGS in the normal way to the "configure" command, in
- order to cross-compile PCRE for some other host. However, during the building
+ order to cross-compile PCRE for some other host. However, you should NOT
- process, the dftables.c source file is compiled *and run* on the local host, in
+ specify --enable-rebuild-chartables, because if you do, the dftables.c source
- order to generate the default character tables (the chartables.c file). It
+ file is compiled and run on the local host, in order to generate the inbuilt
- therefore needs to be compiled with the local compiler, not the cross compiler.
+ character tables (the pcre_chartables.c file). This will probably not work,
- You can do this by specifying CC_FOR_BUILD (and if necessary CFLAGS_FOR_BUILD;
+ because dftables.c needs to be compiled with the local compiler, not the cross
- there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)
+ compiler.
- when calling the "configure" command. If they are not specified, they default
- to the values of CC and CFLAGS.
+ When --enable-rebuild-chartables is not specified, pcre_chartables.c is created
+ by making a copy of pcre_chartables.c.dist, which is a default set of tables
+ that assumes ASCII code. Cross-compiling with the default tables should not be
+ a problem.
+ If you need to modify the character tables when cross-compiling, you should
+ move pcre_chartables.c.dist out of the way, then compile dftables.c by hand and
+ run it on the local host to make a new version of pcre_chartables.c.dist.
+ Then when you cross-compile PCRE this new version of the tables will be used.
  Using HP's ANSI C++ compiler (aCC)
-Line 397 
 running the "configure" script:
+Line 494 
 running the "configure" script:
    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
+ Using Sun's compilers for Solaris
+ ---------------------------------
+ A user reports that the following configurations work on Solaris 9 sparcv9 and
+ Solaris 9 x86 (32-bit):
+   Solaris 9 sparcv9: ./configure --disable-cpp CC=/bin/cc CFLAGS="-m64 -g"
+   Solaris 9 x86:     ./configure --disable-cpp CC=/bin/cc CFLAGS="-g"
+ Using PCRE from MySQL
+ ---------------------
+ On systems where both PCRE and MySQL are installed, it is possible to make use
+ of PCRE from within MySQL, as an alternative to the built-in pattern matching.
+ There is a web page that tells you how to do this:
+   http://www.mysqludf.org/lib_mysqludf_preg/index.php
  Making new tarballs
  -------------------
  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
- zip formats. However, if you have modified any of the man page sources in the
+ zip formats. The command "make distcheck" does the same, but then does a trial
- doc directory, you should first run the PrepareRelease script. This re-creates
+ build of the new distribution to ensure that it works.
- the .txt and HTML forms of the documentation from the man pages.
+ If you have modified any of the man page sources in the doc directory, you
+ should first run the PrepareRelease script before making a distribution. This
+ script creates the .txt and HTML forms of the documentation from the man pages.
  Testing PCRE
-Line 461 
 is output to say why. If running this te
+Line 581 
 is output to say why. If running this te
  in the comparison output, it means that locale is not available on your system,
  despite being listed by "locale". This does not mean that PCRE is broken.
+ [If you are trying to run this test on Windows, you may be able to get it to
+ work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
+ RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
+ Windows versions of test 2. More info on using RunTest.bat is included in the
+ document entitled NON-UNIX-USE.]
  The fourth test checks the UTF-8 support. It is not run automatically unless
  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when
- running "configure". This file can be also fed directly to the perltest script,
+ running "configure". This file can be also fed directly to the perltest.pl
- provided you are running Perl 5.8 or higher. (For Perl 5.6, a small patch,
+ script, provided you are running Perl 5.8 or higher.
- commented in the script, can be be used.)
  The fifth test checks error handling with UTF-8 encoding, and internal UTF-8
  features of PCRE that are not relevant to Perl.
- The sixth test checks the support for Unicode character properties. It it not
+ The sixth test (which is Perl-5.10 compatible) checks the support for Unicode
- run automatically unless PCRE is built with Unicode property support. To to
+ character properties. It it not run automatically unless PCRE is built with
- this you must set --enable-unicode-properties when running "configure".
+ Unicode property support. To to this you must set --enable-unicode-properties
+ when running "configure".
  The seventh, eighth, and ninth tests check the pcre_dfa_exec() alternative
  matching function, in non-UTF-8 mode, UTF-8 mode, and UTF-8 mode with Unicode
  property support, respectively. The eighth and ninth tests are not run
  automatically unless PCRE is build with the relevant support.
+ The tenth test checks some internal offsets and code size features; it is run
+ only when the default "link size" of 2 is set (in other cases the sizes
+ change).
+ The eleventh test checks out features that are new in Perl 5.10, and the
+ twelfth test checks a number internals and non-Perl features concerned with
+ Unicode property support. It it not run automatically unless PCRE is built with
+ Unicode property support. To to this you must set --enable-unicode-properties
+ when running "configure".
  Character tables
  ----------------
-Line 490 
 concatenated tables. A call to pcre_make
+Line 626 
 concatenated tables. A call to pcre_make
  of tables in the current locale. If the final argument for pcre_compile() is
  passed as NULL, a set of default tables that is built into the binary is used.
- The source file called chartables.c contains the default set of tables. This is
+ The source file called pcre_chartables.c contains the default set of tables. By
- not supplied in the distribution, but is built by the program dftables
+ default, this is created as a copy of pcre_chartables.c.dist, which contains
- (compiled from dftables.c), which uses the ANSI C character handling functions
+ tables for ASCII coding. However, if --enable-rebuild-chartables is specified
- such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table
+ for ./configure, a different version of pcre_chartables.c is built by the
- sources. This means that the default C locale which is set for your system will
+ program dftables (compiled from dftables.c), which uses the ANSI C character
- control the contents of these default tables. You can change the default tables
+ handling functions such as isalnum(), isalpha(), isupper(), islower(), etc. to
- by editing chartables.c and then re-building PCRE. If you do this, you should
+ build the table sources. This means that the default C locale which is set for
- take care to ensure that the file does not get automaticaly re-generated.
+ your system will control the contents of these default tables. You can change
+ the default tables by editing pcre_chartables.c and then re-building PCRE. If
+ you do this, you should take care to ensure that the file does not get
+ automatically re-generated. The best way to do this is to move
+ pcre_chartables.c.dist out of the way and replace it with your customized
+ tables.
+ When the dftables program is run as a result of --enable-rebuild-chartables,
+ it uses the default C locale that is set on your system. It does not pay
+ attention to the LC_xxx environment variables. In other words, it uses the
+ system's default locale rather than whatever the compiling user happens to have
+ set. If you really do want to build a source set of character tables in a
+ locale that is specified by the LC_xxx variables, you can run the dftables
+ program by hand with the -L option. For example:
+   ./dftables -L pcre_chartables.c.special
  The first two 256-byte tables provide lower casing and case flipping functions,
  respectively. The next table consists of three 32-byte bit maps which identify
-Line 526 
 The distribution should contain the foll
+Line 677 
 The distribution should contain the foll
  (A) Source files of the PCRE library functions and their headers:
-   dftables.c             auxiliary program for building chartables.c
+   dftables.c              auxiliary program for building pcre_chartables.c
+                             when --enable-rebuild-chartables is specified
-   pcreposix.c            )
+   pcre_chartables.c.dist  a default set of character tables that assume ASCII
-   pcre_compile.c         )
+                             coding; used, unless --enable-rebuild-chartables is
-   pcre_config.c          )
+                             specified, by copying to pcre_chartables.c
-   pcre_dfa_exec.c        )
-   pcre_exec.c            )
+   pcreposix.c             )
-   pcre_fullinfo.c        )
+   pcre_compile.c          )
-   pcre_get.c             ) sources for the functions in the library,
+   pcre_config.c           )
-   pcre_globals.c         )   and some internal functions that they use
+   pcre_dfa_exec.c         )
-   pcre_info.c            )
+   pcre_exec.c             )
-   pcre_maketables.c      )
+   pcre_fullinfo.c         )
-   pcre_newline.c         )
+   pcre_get.c              ) sources for the functions in the library,
-   pcre_ord2utf8.c        )
+   pcre_globals.c          )   and some internal functions that they use
-   pcre_refcount.c        )
+   pcre_info.c             )
-   pcre_study.c           )
+   pcre_maketables.c       )
-   pcre_tables.c          )
+   pcre_newline.c          )
-   pcre_try_flipped.c     )
+   pcre_ord2utf8.c         )
-   pcre_ucp_searchfuncs.c )
+   pcre_refcount.c         )
-   pcre_valid_utf8.c      )
+   pcre_study.c            )
-   pcre_version.c         )
+   pcre_tables.c           )
-   pcre_xclass.c          )
+   pcre_try_flipped.c      )
-   pcre_printint.src      ) debugging function that is #included in pcretest,
+   pcre_ucd.c              )
-                          )   and can also be #included in pcre_compile()
+   pcre_valid_utf8.c       )
-   pcre.h.in              template for pcre.h when built by "configure"
+   pcre_version.c          )
-   pcreposix.h            header for the external POSIX wrapper API
+   pcre_xclass.c           )
-   pcre_internal.h        header for internal use
+   pcre_printint.src       ) debugging function that is #included in pcretest,
-   ucp.h                  ) headers concerned with
+                           )   and can also be #included in pcre_compile()
-   ucpinternal.h          )   Unicode property handling
+   pcre.h.in               template for pcre.h when built by "configure"
-   ucptable.h             ) (this one is the data table)
+   pcreposix.h             header for the external POSIX wrapper API
+   pcre_internal.h         header for internal use
-   config.h.in            template for config.h, which is built by "configure"
+   ucp.h                   header for Unicode property handling
-   pcrecpp.h              public header file for the C++ wrapper
+   config.h.in             template for config.h, which is built by "configure"
-   pcrecpparg.h.in        template for another C++ header file
-   pcre_scanner.h         public header file for C++ scanner functions
+   pcrecpp.h               public header file for the C++ wrapper
-   pcrecpp.cc             )
+   pcrecpparg.h.in         template for another C++ header file
-   pcre_scanner.cc        ) source for the C++ wrapper library
+   pcre_scanner.h          public header file for C++ scanner functions
+   pcrecpp.cc              )
-   pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the
+   pcre_scanner.cc         ) source for the C++ wrapper library
-                            C++ stringpiece functions
-   pcre_stringpiece.cc    source for the C++ stringpiece functions
+   pcre_stringpiece.h.in   template for pcre_stringpiece.h, the header for the
+                             C++ stringpiece functions
+   pcre_stringpiece.cc     source for the C++ stringpiece functions
  (B) Source files for programs that use PCRE:
-   pcredemo.c             simple demonstration of coding calls to PCRE
+   pcredemo.c              simple demonstration of coding calls to PCRE
-   pcregrep.c             source of a grep utility that uses PCRE
+   pcregrep.c              source of a grep utility that uses PCRE
-   pcretest.c             comprehensive test program
+   pcretest.c              comprehensive test program
  (C) Auxiliary files:
-html                script to turn "man" pages into HTML
+html                 script to turn "man" pages into HTML
-   AUTHORS                information about the author of PCRE
+   AUTHORS                 information about the author of PCRE
-   ChangeLog              log of changes to the code
+   ChangeLog               log of changes to the code
-   CleanTxt               script to clean nroff output for txt man pages
+   CleanTxt                script to clean nroff output for txt man pages
-   Detrail                script to remove trailing spaces
+   Detrail                 script to remove trailing spaces
-   HACKING                some notes about the internals of PCRE
+   HACKING                 some notes about the internals of PCRE
-   INSTALL                generic installation instructions
+   INSTALL                 generic installation instructions
-   LICENCE                conditions for the use of PCRE
+   LICENCE                 conditions for the use of PCRE
-   COPYING                the same, using GNU's standard name
+   COPYING                 the same, using GNU's standard name
-   Makefile.in            ) template for Unix Makefile, which is built by
+   Makefile.in             ) template for Unix Makefile, which is built by
-                          )   "configure"
+                           )   "configure"
-   Makefile.am            ) the automake input that was used to create
+   Makefile.am             ) the automake input that was used to create
-                          )   Makefile.in
+                           )   Makefile.in
-   NEWS                   important changes in this release
+   NEWS                    important changes in this release
-   NON-UNIX-USE           notes on building PCRE on non-Unix systems
+   NON-UNIX-USE            notes on building PCRE on non-Unix systems
-   PrepareRelease         script to make preparations for "make dist"
+   PrepareRelease          script to make preparations for "make dist"
-   README                 this file
+   README                  this file
-   RunTest.in             template for a Unix shell script for running tests
+   RunTest                 a Unix shell script for running tests
-   RunGrepTest.in         template for a Unix shell script for pcregrep tests
+   RunGrepTest             a Unix shell script for pcregrep tests
-   aclocal.m4             m4 macros (generated by "aclocal")
+   aclocal.m4              m4 macros (generated by "aclocal")
-   config.guess           ) files used by libtool,
+   config.guess            ) files used by libtool,
-   config.sub             )   used only when building a shared library
+   config.sub              )   used only when building a shared library
-   configure              a configuring shell script (built by autoconf)
+   configure               a configuring shell script (built by autoconf)
-   configure.ac           ) the autoconf input that was used to build
+   configure.ac            ) the autoconf input that was used to build
-                          )   "configure" and config.h
+                           )   "configure" and config.h
-   depcomp                ) script to find program dependencies, generated by
+   depcomp                 ) script to find program dependencies, generated by
-                          )   automake
+                           )   automake
-   doc/*.3                man page sources for the PCRE functions
+   doc/*.3                 man page sources for PCRE
-   doc/*.1                man page sources for pcregrep and pcretest
+   doc/*.1                 man page sources for pcregrep and pcretest
-   doc/index.html.src     the base HTML page
+   doc/index.html.src      the base HTML page
-   doc/html/*             HTML documentation
+   doc/html/*              HTML documentation
-   doc/pcre.txt           plain text version of the man pages
+   doc/pcre.txt            plain text version of the man pages
-   doc/pcretest.txt       plain text documentation of test program
+   doc/pcretest.txt        plain text documentation of test program
-   doc/perltest.txt       plain text documentation of Perl test program
+   doc/perltest.txt        plain text documentation of Perl test program
-   install-sh             a shell script for installing files
+   install-sh              a shell script for installing files
-   libpcre.pc.in          template for libpcre.pc for pkg-config
+   libpcre.pc.in           template for libpcre.pc for pkg-config
-   libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config
+   libpcreposix.pc.in      template for libpcreposix.pc for pkg-config
-   ltmain.sh              file used to build a libtool script
+   libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
-   missing                ) common stub for a few missing GNU programs while
+   ltmain.sh               file used to build a libtool script
-                          )   installing, generated by automake
+   missing                 ) common stub for a few missing GNU programs while
-   mkinstalldirs          script for making install directories
+                           )   installing, generated by automake
-   perltest.pl            Perl test program
+   mkinstalldirs           script for making install directories
-   pcre-config.in         source of script which retains PCRE information
+   perltest.pl             Perl test program
+   pcre-config.in          source of script which retains PCRE information
    pcrecpp_unittest.cc          )
    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
    pcre_stringpiece_unittest.cc )
-   testdata/testinput*    test data for main library tests
+   testdata/testinput*     test data for main library tests
-   testdata/testoutput*   expected test results
+   testdata/testoutput*    expected test results
-   testdata/grep*         input and output for pcregrep tests
+   testdata/grep*          input and output for pcregrep tests
  (D) Auxiliary files for cmake support
+   cmake/COPYING-CMAKE-SCRIPTS
+   cmake/FindPackageHandleStandardArgs.cmake
+   cmake/FindReadline.cmake
    CMakeLists.txt
    config-cmake.h.in
  (E) Auxiliary files for VPASCAL
    makevp.bat
-   makevp-compile.txt
+   makevp_c.txt
-   makevp-linklib.txt
+   makevp_l.txt
    pcregexp.pas
  (F) Auxiliary files for building PCRE "by hand"
-   pcre.h.generic         ) a version of the public PCRE header file
+   pcre.h.generic          ) a version of the public PCRE header file
-                          )   for use in non-"configure" environments
+                           )   for use in non-"configure" environments
-   config.h.generic       ) a version of config.h for use in non-"configure"
+   config.h.generic        ) a version of config.h for use in non-"configure"
-                          )   environments
+                           )   environments
  (F) Miscellaneous
-Line 653 
 The distribution should contain the foll
+Line 811 
 The distribution should contain the foll
  Philip Hazel
  Email local part: ph10
  Email domain: cam.ac.uk
- Last updated: March 2007
+ Last updated: 02 August 2011

 Legend:



Removed from v.127
 


changed lines


 
Added in v.654
 Legend:



Removed from v.127
 


changed lines


 
Added in v.654
-Removed from v.127
+Added in v.654

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12