/[pcre]/code/trunk/README

Diff of /code/trunk/README

Parent Directory | Revision Log | View Patch Patch

-revision 93 by nigel,
Sat Feb 24 21:41:42 2007 UTC
+revision 127 by ph10,
Mon Mar 19 11:44:45 2007 UTC
 Line 5 
 The latest release of PCRE is always ava
    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
+ There is a mailing list for discussion about the development of PCRE at
+   pcre-dev@exim.org
  Please read the NEWS file if you are upgrading from a previous release.
+ The contents of this README file are:
+   The PCRE APIs
+   Documentation for PCRE
+   Contributions by users of PCRE
+   Building PCRE on non-Unix systems
+   Building PCRE on Unix-like systems
+   Retrieving configuration information on Unix-like systems
+   Shared libraries on Unix-like systems
+   Cross-compiling on Unix-like systems
+   Using HP's ANSI C++ compiler (aCC)
+   Making new tarballs
+   Testing PCRE
+   Character tables
+   File manifest
  The PCRE APIs
-Line 15 
 PCRE is written in C, and it has its own
+Line 34 
 PCRE is written in C, and it has its own
  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page
  for details).
- Also included are a set of C wrapper functions that are based on the POSIX
+ Also included in the distribution are a set of C wrapper functions that are
- API. These end up in the library called libpcreposix. Note that this just
+ based on the POSIX API. These end up in the library called libpcreposix. Note
- provides a POSIX calling interface to PCRE: the regular expressions themselves
+ that this just provides a POSIX calling interface to PCRE; the regular
- still follow Perl syntax and semantics. The header file for the POSIX-style
+ expressions themselves still follow Perl syntax and semantics. The POSIX API is
- functions is called pcreposix.h. The official POSIX name is regex.h, but I
+ restricted, and does not give full access to all of PCRE's facilities.
- didn't want to risk possible problems with existing files of that name by
- distributing it that way. To use it with an existing program that uses the
+ The header file for the POSIX-style functions is called pcreposix.h. The
- POSIX API, it will have to be renamed or pointed at by a link.
+ official POSIX name is regex.h, but I did not want to risk possible problems
+ with existing files of that name by distributing it that way. To use PCRE with
+ an existing program that uses the POSIX API, pcreposix.h will have to be
+ renamed or pointed at by a link.
  If you are using the POSIX interface to PCRE and there is already a POSIX regex
- library installed on your system, you must take care when linking programs to
+ library installed on your system, as well as worrying about the regex.h header
+ file (as mentioned above), you must also take care when linking programs to
  ensure that they link with PCRE's libpcreposix library. Otherwise they may pick
- up the "real" POSIX functions of the same name.
+ up the POSIX functions of the same name from the other library.
+ One way of avoiding this confusion is to compile PCRE with the addition of
+ -Dregcomp=PCREregcomp (and similarly for the other POSIX functions) to the
+ compiler flags (CFLAGS if you are using "configure" -- see below). This has the
+ effect of renaming the functions so that the names no longer clash. Of course,
+ you have to do the same thing for your applications, or write them using the
+ new names.
  Documentation for PCRE
  ----------------------
- If you install PCRE in the normal way, you will end up with an installed set of
+ If you install PCRE in the normal way on a Unix-like system, you will end up
- man pages whose names all start with "pcre". The one that is just called "pcre"
+ with a set of man pages whose names all start with "pcre". The one that is just
- lists all the others. In addition to these man pages, the PCRE documentation is
+ called "pcre" lists all the others. In addition to these man pages, the PCRE
- supplied in two other forms; however, as there is no standard place to install
+ documentation is supplied in two other forms:
- them, they are left in the doc directory of the unpacked source distribution.
- These forms are:
+. There are files called doc/pcre.txt, doc/pcregrep.txt, and
+      doc/pcretest.txt in the source distribution. The first of these is a
-. Files called doc/pcre.txt, doc/pcregrep.txt, and doc/pcretest.txt. The
+      concatenation of the text forms of all the section 3 man pages except
-      first of these is a concatenation of the text forms of all the section 3
+      those that summarize individual functions. The other two are the text
-      man pages except those that summarize individual functions. The other two
+      forms of the section 1 man pages for the pcregrep and pcretest commands.
-      are the text forms of the section 1 man pages for the pcregrep and
+      These text forms are provided for ease of scanning with text editors or
-      pcretest commands. Text forms are provided for ease of scanning with text
+      similar tools. They are installed in <prefix>/share/doc/pcre, where
-      editors or similar tools.
+      <prefix> is the installation prefix (defaulting to /usr/local).
-. A subdirectory called doc/html contains all the documentation in HTML
+. A set of files containing all the documentation in HTML form, hyperlinked
-      form, hyperlinked in various ways, and rooted in a file called
+      in various ways, and rooted in a file called index.html, is distributed in
-      doc/index.html.
+      doc/html and installed in <prefix>/share/doc/pcre/html.
  Contributions by users of PCRE
-Line 59 
 You can find contributions from PCRE use
+Line 89 
 You can find contributions from PCRE use
    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
- where there is also a README file giving brief descriptions of what they are.
+ There is a README file giving brief descriptions of what they are. Some are
- Several of them provide support for compiling PCRE on various flavours of
+ complete in themselves; others are pointers to URLs containing relevant files.
- Windows systems (I myself do not use Windows). Some are complete in themselves;
+ Some of this material is likely to be well out-of-date. In particular, several
- others are pointers to URLs containing relevant files.
+ of the contributions provide support for compiling PCRE on various flavours of
+ Windows (I myself do not use Windows), but nowadays there is more Windows
+ support in the standard distribution.
+ Building PCRE on non-Unix systems
+ ---------------------------------
- Building PCRE on a Unix-like system
+ 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.
+ 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
+ library, because it uses only Standard C functions.
+ 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.
-Line 75 
 To build PCRE on a Unix-like system, fir
+Line 119 
 To build PCRE on a Unix-like system, fir
  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
  "autoconf" configuration script, for which generic instructions are supplied in
- INSTALL.
+ the file INSTALL.
  Most commonly, people build PCRE within its own distribution directory, and in
- this case, on many systems, just running "./configure" is sufficient, but the
+ this case, on many systems, just running "./configure" is sufficient. However,
- usual methods of changing standard defaults are available. For example:
+ the usual methods of changing standard defaults are available. For example:
  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
-Line 126 
 library. You can read more about them in
+Line 170 
 library. You can read more about them in
    --newline-is-cr or --newline-is-lf or --newline-is-crlf or --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
+   the files are edited to change the line endings, there are likely to be some
+   failures. With --newline-is-any, many tests should succeed, but there may be
+   some failures.
  . 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,
-Line 141 
 library. You can read more about them in
+Line 191 
 library. You can read more about them in
    --with-match-limit=500000
    on the "configure" command. This is just the default; individual calls to
-   pcre_exec() can supply their own value. There is discussion on the pcreapi
+   pcre_exec() can supply their own value. There is more discussion on the
-   man page.
+   pcreapi man page.
  . There is a separate counter that limits the depth of recursive function calls
    during a matching process. This also has a default of ten million, which is
-Line 157 
 library. You can read more about them in
+Line 207 
 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. If you build PCRE with an increased link size, test 2
+   ever to be necessary.
-   (and 5 if you are using UTF-8) will fail. Part of the output of these tests
-   is a representation of the compiled pattern, and this changes with the link
-   size.
  . You can build PCRE so that its internal match() function that is called from
-   pcre_exec() does not call itself recursively. Instead, it uses blocks of data
+   pcre_exec() does not call itself recursively. Instead, it uses memory blocks
-   from the heap via special functions pcre_stack_malloc() and pcre_stack_free()
+   obtained from the heap via the special functions pcre_stack_malloc() and
-   to save data that would otherwise be saved on the stack. To build PCRE like
+   pcre_stack_free() to save data that would otherwise be saved on the stack. To
-   this, use
+   build PCRE like this, use
    --disable-stack-for-recursion
    on the "configure" command. PCRE runs more slowly in this mode, but it may be
    necessary in environments with limited stack sizes. This applies only to the
    pcre_exec() function; it does not apply to pcre_dfa_exec(), which does not
-   use deeply nested recursion.
+   use deeply nested recursion. There is a discussion about stack sizes in the
+   pcrestack man page.
- The "configure" script builds eight files for the basic C library:
+ The "configure" script builds the following files for the basic C library:
  . Makefile is the makefile that builds the library
  . config.h contains build-time configuration options for the library
+ . pcre.h is the public PCRE header file
  . pcre-config is a script that shows the settings of "configure" options
  . libpcre.pc is data for the pkg-config command
  . libtool is a script that builds shared and/or static libraries
- . RunTest is a script for running tests on the library
+ . RunTest is a script for running tests on the basic C library
  . RunGrepTest is a script for running tests on the pcregrep command
- In addition, if a C++ compiler is found, the following are also built:
+ Versions of config.h and pcre.h are distributed in the PCRE tarballs under
+ the names config.h.generic and pcre.h.generic. These are provided for the
+ benefit of those who have to built PCRE without the benefit of "configure". If
+ you use "configure", the .generic versions are not used.
- . pcrecpp.h is the header file for programs that call PCRE via the C++ wrapper
+ If a C++ compiler is found, the following files are also built:
+ . libpcrecpp.pc is data for the pkg-config command
+ . pcrecpparg.h is a header file for programs that call PCRE via the C++ wrapper
  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions
  The "configure" script also creates config.status, which is an executable
-Line 195 
 script that can be run to recreate the c
+Line 250 
 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, and the pcregrep
+ libpcre and libpcreposix, a test program called pcretest, a demonstration
- command. If a C++ compiler was found on your system, it also builds the C++
+ program called pcredemo, and the pcregrep command. If a C++ compiler was found
- wrapper library, which is called libpcrecpp, and some test programs called
+ on your system, "make" also builds the C++ wrapper library, which is called
- pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
+ libpcrecpp, and some test programs called pcrecpp_unittest,
+ pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper
- The command "make test" runs all the appropriate tests. Details of the PCRE
+ can be disabled by adding --disable-cpp to the "configure" command.
- tests are given in a separate section of this document, below.
+ The command "make check" runs all the appropriate tests. Details of the PCRE
- You can use "make install" to copy the libraries, the public header files
+ tests are given below in a separate section of this document.
- pcre.h, pcreposix.h, pcrecpp.h, and pcre_stringpiece.h (the last two only if
- the C++ wrapper was built), and the man pages to appropriate live directories
+ You can use "make install" to install PCRE into live directories on your
- on your system, in the normal way.
+ system. The following are installed (file names are all relative to the
+ <prefix> that is set when "configure" is run):
+   Commands (bin):
+     pcretest
+     pcregrep
+     pcre-config
+   Libraries (lib):
+     libpcre
+     libpcreposix
+     libpcrecpp (if C++ support is enabled)
+   Configuration information (lib/pkgconfig):
+     libpcre.pc
+     libpcrecpp.pc (if C++ support is enabled)
+   Header files (include):
+     pcre.h
+     pcreposix.h
+     pcre_scanner.h      )
+     pcre_stringpiece.h  ) if C++ support is enabled
+     pcrecpp.h           )
+     pcrecpparg.h        )
+   Man pages (share/man/man{1,3}):
+     pcregrep.1
+     pcretest.1
+     pcre.3
+     pcre*.3 (lots more pages, all starting "pcre")
+   HTML documentation (share/doc/pcre/html):
+     index.html
+     *.html (lots more pages, hyperlinked from index.html)
+   Text file documentation (share/doc/pcre):
+     AUTHORS
+     COPYING
+     ChangeLog
+     LICENCE
+     NEWS
+     README
+     pcre.txt       (a concatenation of the man(3) pages)
+     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
-Line 216 
 remove any directories, because these ar
+Line 318 
 remove any directories, because these ar
  Retrieving configuration information on Unix-like systems
  ---------------------------------------------------------
- Running "make install" also installs the command pcre-config, which can be used
+ Running "make install" installs the command pcre-config, which can be used to
- to recall information about the PCRE configuration and installation. For
+ recall information about the PCRE configuration and installation. For example:
- example:
    pcre-config --version
-Line 237 
 single command is used. For example:
+Line 338 
 single command is used. For example:
    pkg-config --cflags pcre
  The data is held in *.pc files that are installed in a directory called
- pkgconfig.
+ <prefix>/lib/pkgconfig.
  Shared libraries on Unix-like systems
-Line 254 
 built. The programs pcretest and pcregre
+Line 355 
 built. The programs pcretest and pcregre
  libraries (by means of wrapper scripts in the case of shared libraries). When
  you use "make install" to install shared libraries, pcregrep and pcretest are
  automatically re-built to use the newly installed shared libraries before being
- installed themselves. However, the versions left in the source directory still
+ installed themselves. However, the versions left in the build directory still
  use the uninstalled libraries.
  To build PCRE using static libraries only you must use --disable-shared when
-Line 266 
 Then run "make" in the usual way. Simila
+Line 367 
 Then run "make" in the usual way. Simila
  build only shared libraries.
- Cross-compiling on a Unix-like system
+ 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
-Line 284 
 Using HP's ANSI C++ compiler (aCC)
+Line 385 
 Using HP's ANSI C++ compiler (aCC)
  ----------------------------------
  Unless C++ support is disabled by specifying the "--disable-cpp" option of the
- "configure" script, you *must* include the "-AA" option in the CXXFLAGS
+ "configure" script, you must include the "-AA" option in the CXXFLAGS
  environment variable in order for the C++ components to compile correctly.
  Also, note that the aCC compiler on PA-RISC platforms may have a defect whereby
-Line 296 
 running the "configure" script:
+Line 397 
 running the "configure" script:
    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
- Building on non-Unix systems
+ Making new tarballs
- ----------------------------
+ -------------------
- For a non-Unix system, read the comments in the file NON-UNIX-USE, though if
+ The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
- the system supports the use of "configure" and "make" you may be able to build
+ zip formats. However, if you have modified any of the man page sources in the
- PCRE in the same way as for Unix systems.
+ doc directory, you should first run the PrepareRelease script. This re-creates
+ the .txt and HTML forms of the documentation from the man pages.
- PCRE has been compiled on Windows systems and on Macintoshes, but I don't know
- the details because I don't use those systems. It should be straightforward to
- build PCRE on any system that has a Standard C compiler and library, because it
- uses only Standard C functions.
  Testing PCRE
  ------------
- To test PCRE on a Unix system, run the RunTest script that is created by the
+ To test the basic PCRE library on a Unix system, run the RunTest script that is
- configuring process. There is also a script called RunGrepTest that tests the
+ created by the configuring process. There is also a script called RunGrepTest
- options of the pcregrep command. If the C++ wrapper library is build, three
+ that tests the options of the pcregrep command. If the C++ wrapper library is
- test programs called pcrecpp_unittest, pcre_scanner_unittest, and
+ built, three test programs called pcrecpp_unittest, pcre_scanner_unittest, and
- pcre_stringpiece_unittest are provided.
+ pcre_stringpiece_unittest are also built.
- Both the scripts and all the program tests are run if you obey "make runtest",
+ Both the scripts and all the program tests are run if you obey "make check" or
- "make check", or "make test". For other systems, see the instructions in
+ "make test". For other systems, see the instructions in NON-UNIX-USE.
- NON-UNIX-USE.
  The RunTest script runs the pcretest test program (which is documented in its
- own man page) on each of the testinput files (in the testdata directory) in
+ own man page) on each of the testinput files in the testdata directory in
  turn, and compares the output with the contents of the corresponding testoutput
  files. A file called testtry is used to hold the main output from pcretest
  (testsavedregex is also used as a working file). To run pcretest on just one of
-Line 331 
 the test files, give its number as an ar
+Line 427 
 the test files, give its number as an ar
    RunTest 2
- The first test file can also be fed directly into the perltest script to check
+ The first test file can also be fed directly into the perltest.pl script to
- that Perl gives the same results. The only difference you should see is in the
+ check that Perl gives the same results. The only difference you should see is
- first few lines, where the Perl version is given instead of the PCRE version.
+ in the first few lines, where the Perl version is given instead of the PCRE
+ version.
  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),
  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
  detection, and run-time flags that are specific to PCRE, as well as the POSIX
- wrapper API. It also uses the debugging flag to check some of the internals of
+ wrapper API. It also uses the debugging flags to check some of the internals of
  pcre_compile().
  If you build PCRE with a locale setting that is not the standard C locale, the
-Line 373 
 commented in the script, can be be used.
+Line 470 
 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 and test checks the support for Unicode character properties. It it
+ The sixth test checks the support for Unicode character properties. It it not
- not run automatically unless PCRE is built with Unicode property support. To to
+ run automatically unless PCRE is built with 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
-Line 386 
 automatically unless PCRE is build with
+Line 483 
 automatically unless PCRE is build with
  Character tables
  ----------------
- PCRE uses four tables for manipulating and identifying characters whose values
+ For speed, PCRE uses four tables for manipulating and identifying characters
- are less than 256. The final argument of the pcre_compile() function is a
+ whose code point values are less than 256. The final argument of the
- pointer to a block of memory containing the concatenated tables. A call to
+ pcre_compile() function is a pointer to a block of memory containing the
- pcre_maketables() can be used to generate a set of tables in the current
+ concatenated tables. A call to pcre_maketables() can be used to generate a set
- locale. If the final argument for pcre_compile() is passed as NULL, a set of
+ of tables in the current locale. If the final argument for pcre_compile() is
- default tables that is built into the binary is used.
+ 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
  not supplied in the distribution, but is built by the program dftables
-Line 400 
 such as isalnum(), isalpha(), isupper(),
+Line 497 
 such as isalnum(), isalpha(), isupper(),
  sources. This means that the default C locale which is set for your system will
  control the contents of these default tables. You can change the default tables
  by editing chartables.c and then re-building PCRE. If you do this, you should
- probably also edit Makefile to ensure that the file doesn't ever get
+ take care to ensure that the file does not get automaticaly re-generated.
- re-generated.
  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
  digits, "word" characters, and white space, respectively. These are used when
- building 32-byte bit maps that represent character classes.
+ building 32-byte bit maps that represent character classes for code points less
+ than 256.
  The final 256-byte table has bits indicating various character types, as
  follows:
-Line 422 
 You should not alter the set of characte
+Line 519 
 You should not alter the set of characte
  will cause PCRE to malfunction.
- Manifest
+ File manifest
- --------
+ -------------
  The distribution should contain the following files:
- (A) The actual source files of the PCRE library functions and their
+ (A) Source files of the PCRE library functions and their headers:
-     headers:
-   dftables.c            auxiliary program for building chartables.c
+   dftables.c             auxiliary program for building chartables.c
-   pcreposix.c           )
+   pcreposix.c            )
-   pcre_compile.c        )
+   pcre_compile.c         )
-   pcre_config.c         )
+   pcre_config.c          )
-   pcre_dfa_exec.c       )
+   pcre_dfa_exec.c        )
-   pcre_exec.c           )
+   pcre_exec.c            )
-   pcre_fullinfo.c       )
+   pcre_fullinfo.c        )
-   pcre_get.c            ) sources for the functions in the library,
+   pcre_get.c             ) sources for the functions in the library,
-   pcre_globals.c        )   and some internal functions that they use
+   pcre_globals.c         )   and some internal functions that they use
-   pcre_info.c           )
+   pcre_info.c            )
-   pcre_maketables.c     )
+   pcre_maketables.c      )
-   pcre_newline.c        )
+   pcre_newline.c         )
-   pcre_ord2utf8.c       )
+   pcre_ord2utf8.c        )
-   pcre_refcount.c       )
+   pcre_refcount.c        )
-   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_ucp_searchfuncs.c )
-   pcre_valid_utf8.c     )
+   pcre_valid_utf8.c      )
-   pcre_version.c        )
+   pcre_version.c         )
-   pcre_xclass.c         )
+   pcre_xclass.c          )
-   ucptable.c            )
+   pcre_printint.src      ) debugging function that is #included in pcretest,
+                          )   and can also be #included in pcre_compile()
-   pcre_printint.src     ) debugging function that is #included in pcretest, and
+   pcre.h.in              template for pcre.h when built by "configure"
-                         )   can also be #included in pcre_compile()
+   pcreposix.h            header for the external POSIX wrapper API
+   pcre_internal.h        header for internal use
-   pcre.h                the public PCRE header file
+   ucp.h                  ) headers concerned with
-   pcreposix.h           header for the external POSIX wrapper API
+   ucpinternal.h          )   Unicode property handling
-   pcre_internal.h       header for internal use
+   ucptable.h             ) (this one is the data table)
-   ucp.h                 ) headers concerned with
-   ucpinternal.h         )   Unicode property handling
+   config.h.in            template for config.h, which is built by "configure"
-   config.in             template for config.h, which is built by configure
+   pcrecpp.h              public header file for the C++ wrapper
-   pcrecpp.h             the header file for the C++ wrapper
+   pcrecpparg.h.in        template for another C++ header file
-   pcrecpparg.h.in       "source" for another C++ header file
+   pcre_scanner.h         public header file for C++ scanner functions
-   pcrecpp.cc            )
+   pcrecpp.cc             )
-   pcre_scanner.cc       ) source for the C++ wrapper library
+   pcre_scanner.cc        ) source for the C++ wrapper library
-   pcre_stringpiece.h.in "source" for pcre_stringpiece.h, the header for the
+   pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the
-                           C++ stringpiece functions
+                            C++ stringpiece functions
-   pcre_stringpiece.cc   source for the C++ stringpiece functions
+   pcre_stringpiece.cc    source for the C++ stringpiece functions
- (B) Auxiliary files:
+ (B) Source files for programs that use PCRE:
-   AUTHORS               information about the author of PCRE
+   pcredemo.c             simple demonstration of coding calls to PCRE
-   ChangeLog             log of changes to the code
+   pcregrep.c             source of a grep utility that uses PCRE
-   INSTALL               generic installation instructions
+   pcretest.c             comprehensive test program
-   LICENCE               conditions for the use of PCRE
-   COPYING               the same, using GNU's standard name
+ (C) Auxiliary files:
-   Makefile.in           template for Unix Makefile, which is built by configure
-   NEWS                  important changes in this release
+html                script to turn "man" pages into HTML
-   NON-UNIX-USE          notes on building PCRE on non-Unix systems
+   AUTHORS                information about the author of PCRE
-   README                this file
+   ChangeLog              log of changes to the code
-   RunTest.in            template for a Unix shell script for running tests
+   CleanTxt               script to clean nroff output for txt man pages
-   RunGrepTest.in        template for a Unix shell script for pcregrep tests
+   Detrail                script to remove trailing spaces
-   config.guess          ) files used by libtool,
+   HACKING                some notes about the internals of PCRE
-   config.sub            )   used only when building a shared library
+   INSTALL                generic installation instructions
-   config.h.in           "source" for the config.h header file
+   LICENCE                conditions for the use of PCRE
-   configure             a configuring shell script (built by autoconf)
+   COPYING                the same, using GNU's standard name
-   configure.ac          the autoconf input used to build configure
+   Makefile.in            ) template for Unix Makefile, which is built by
-   doc/Tech.Notes        notes on the encoding
+                          )   "configure"
-   doc/*.3               man page sources for the PCRE functions
+   Makefile.am            ) the automake input that was used to create
-   doc/*.1               man page sources for pcregrep and pcretest
+                          )   Makefile.in
-   doc/html/*            HTML documentation
+   NEWS                   important changes in this release
-   doc/pcre.txt          plain text version of the man pages
+   NON-UNIX-USE           notes on building PCRE on non-Unix systems
-   doc/pcretest.txt      plain text documentation of test program
+   PrepareRelease         script to make preparations for "make dist"
-   doc/perltest.txt      plain text documentation of Perl test program
+   README                 this file
-   install-sh            a shell script for installing files
+   RunTest.in             template for a Unix shell script for running tests
-   libpcre.pc.in         "source" for libpcre.pc for pkg-config
+   RunGrepTest.in         template for a Unix shell script for pcregrep tests
-   ltmain.sh             file used to build a libtool script
+   aclocal.m4             m4 macros (generated by "aclocal")
-   mkinstalldirs         script for making install directories
+   config.guess           ) files used by libtool,
-   pcretest.c            comprehensive test program
+   config.sub             )   used only when building a shared library
-   pcredemo.c            simple demonstration of coding calls to PCRE
+   configure              a configuring shell script (built by autoconf)
-   perltest              Perl test program
+   configure.ac           ) the autoconf input that was used to build
-   pcregrep.c            source of a grep utility that uses PCRE
+                          )   "configure" and config.h
-   pcre-config.in        source of script which retains PCRE information
+   depcomp                ) script to find program dependencies, generated by
-   pcrecpp_unittest.c           )
+                          )   automake
-   pcre_scanner_unittest.c      ) test programs for the C++ wrapper
+   doc/*.3                man page sources for the PCRE functions
-   pcre_stringpiece_unittest.c  )
+   doc/*.1                man page sources for pcregrep and pcretest
-   testdata/testinput*   test data for main library tests
+   doc/index.html.src     the base HTML page
-   testdata/testoutput*  expected test results
+   doc/html/*             HTML documentation
-   testdata/grep*        input and output for pcregrep tests
+   doc/pcre.txt           plain text version of the man pages
+   doc/pcretest.txt       plain text documentation of test program
+   doc/perltest.txt       plain text documentation of Perl test program
+   install-sh             a shell script for installing files
+   libpcre.pc.in          template for libpcre.pc for pkg-config
+   libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config
+   ltmain.sh              file used to build a libtool script
+   missing                ) common stub for a few missing GNU programs while
+                          )   installing, generated by automake
+   mkinstalldirs          script for making install directories
+   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/testoutput*   expected test results
+   testdata/grep*         input and output for pcregrep tests
- (C) Auxiliary files for Win32 DLL
+ (D) Auxiliary files for cmake support
-   libpcre.def
+   CMakeLists.txt
-   libpcreposix.def
+   config-cmake.h.in
- (D) Auxiliary file for VPASCAL
+ (E) Auxiliary files for VPASCAL
    makevp.bat
+   makevp-compile.txt
+   makevp-linklib.txt
+   pcregexp.pas
+ (F) Auxiliary files for building PCRE "by hand"
+   pcre.h.generic         ) a version of the public PCRE header file
+                          )   for use in non-"configure" environments
+   config.h.generic       ) a version of config.h for use in non-"configure"
+                          )   environments
+ (F) Miscellaneous
+   RunTest.bat            a script for running tests under Windows
  Philip Hazel
  Email local part: ph10
  Email domain: cam.ac.uk
- November 2006
+ Last updated: March 2007

 Legend:



Removed from v.93
 


changed lines


 
Added in v.127
 Legend:



Removed from v.93
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.5