/[pcre]/code/trunk/README
ViewVC logotype

Diff of /code/trunk/README

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

revision 101 by ph10, Tue Mar 6 15:19:44 2007 UTC revision 109 by ph10, Wed Mar 7 15:35:57 2007 UTC
# Line 6  The latest release of PCRE is always ava Line 6  The latest release of PCRE is always ava
6    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
7    
8  Please read the NEWS file if you are upgrading from a previous release.  Please read the NEWS file if you are upgrading from a previous release.
9    The contents of this README file are:
10    
11      The PCRE APIs
12      Documentation for PCRE
13      Contributions by users of PCRE
14      Building PCRE on non-Unix systems
15      Building PCRE on a Unix-like system
16      Retrieving configuration information on a Unix-like system
17      Shared libraries on Unix-like systems
18      Cross-compiling on a Unix-like system
19      Using HP's ANSI C++ compiler (aCC)
20      Testing PCRE
21      Character tables
22      File manifest
23    
24    
25  The PCRE APIs  The PCRE APIs
# Line 15  PCRE is written in C, and it has its own Line 29  PCRE is written in C, and it has its own
29  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page
30  for details).  for details).
31    
32  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
33  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
34  provides a POSIX calling interface to PCRE: the regular expressions themselves  that this just provides a POSIX calling interface to PCRE; the regular
35  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
36  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.
37  didn't want to risk possible problems with existing files of that name by  
38  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
39  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
40    with existing files of that name by distributing it that way. To use PCRE with
41    an existing program that uses the POSIX API, pcreposix.h will have to be
42    renamed or pointed at by a link.
43    
44  If you are using the POSIX interface to PCRE and there is already a POSIX regex  If you are using the POSIX interface to PCRE and there is already a POSIX regex
45  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
46    file (as mentioned above), you must also take care when linking programs to
47  ensure that they link with PCRE's libpcreposix library. Otherwise they may pick  ensure that they link with PCRE's libpcreposix library. Otherwise they may pick
48  up the "real" POSIX functions of the same name.  up the POSIX functions of the same name from the other library.
49    
50    One way of avoiding this confusion is to compile PCRE with the addition of
51    -Dregcomp=PCREregcomp (and similarly for the other functions) to the compiler
52    flags (CFLAGS if you are using "configure" -- see below). This has the effect
53    of renaming the functions so that the names no longer clash. Of course, you
54    have to do the same thing for your applications, or write them using the new
55    names.
56    
57    
58  Documentation for PCRE  Documentation for PCRE
# Line 36  Documentation for PCRE Line 61  Documentation for PCRE
61  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, you will end up with an installed set of
62  man pages whose names all start with "pcre". The one that is just called "pcre"  man pages whose names all start with "pcre". The one that is just called "pcre"
63  lists all the others. In addition to these man pages, the PCRE documentation is  lists all the others. In addition to these man pages, the PCRE documentation is
64  supplied in two other forms; however, as there is no standard place to install  supplied in two other forms:
65  them, they are left in the doc directory of the unpacked source distribution.  
66  These forms are:    1. There are files called doc/pcre.txt, doc/pcregrep.txt, and
67         doc/pcretest.txt in the source distribution. The first of these is a
68    1. 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
69       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
70       man pages except those that summarize individual functions. The other two       forms of the section 1 man pages for the pcregrep and pcretest commands.
71       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
72       pcretest commands. Text forms are provided for ease of scanning with text       similar tools.
73       editors or similar tools.  
74      2. A set of files containing all the documentation in HTML form, hyperlinked
75    2. A subdirectory called doc/html contains all the documentation in HTML       in various ways, and rooted in a file called index.html, is installed in
76       form, hyperlinked in various ways, and rooted in a file called       the directory <prefix>/share/doc/pcre/html, where <prefix> is the
77       doc/index.html.       installation prefix (defaulting to /usr/local).
78    
79    
80  Contributions by users of PCRE  Contributions by users of PCRE
# Line 60  You can find contributions from PCRE use Line 85  You can find contributions from PCRE use
85    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
86    
87  where there is also a README file giving brief descriptions of what they are.  where there is also a README file giving brief descriptions of what they are.
88  Several of them provide support for compiling PCRE on various flavours of  Some are complete in themselves; others are pointers to URLs containing
89  Windows systems (I myself do not use Windows). Some are complete in themselves;  relevant files. Some of this material is likely to be well out-of-date. In
90  others are pointers to URLs containing relevant files.  particular, several of the contributions provide support for compiling PCRE on
91    various flavours of Windows (I myself do not use Windows), but it is hoped that
92    more Windows support will find its way into the standard distribution.
93    
94    
95  Building on non-Unix systems  Building PCRE on non-Unix systems
96  ----------------------------  ---------------------------------
97    
98  For a non-Unix system, read the comments in the file NON-UNIX-USE, though if  For a non-Unix system, read the comments in the file NON-UNIX-USE, though if
99  the system supports the use of "configure" and "make" you may be able to build  the system supports the use of "configure" and "make" you may be able to build
100  PCRE in the same way as for Unix systems.  PCRE in the same way as for Unix-like systems.
101    
102  PCRE has been compiled on Windows systems and on Macintoshes, but I don't know  PCRE has been compiled on many different operating systems. It should be
103  the details because I don't use those systems. It should be straightforward to  straightforward to build PCRE on any system that has a Standard C compiler and
104  build PCRE on any system that has a Standard C compiler and library, because it  library, because it uses only Standard C functions.
 uses only Standard C functions.  
105    
106    
107  Building PCRE on a Unix-like system  Building PCRE on a Unix-like system
# Line 91  where you want the files to be created. Line 117  where you want the files to be created.
117  INSTALL.  INSTALL.
118    
119  Most commonly, people build PCRE within its own distribution directory, and in  Most commonly, people build PCRE within its own distribution directory, and in
120  this case, on many systems, just running "./configure" is sufficient, but the  this case, on many systems, just running "./configure" is sufficient. However,
121  usual methods of changing standard defaults are available. For example:  the usual methods of changing standard defaults are available. For example:
122    
123  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
124    
# Line 138  library. You can read more about them in Line 164  library. You can read more about them in
164    (the Unix standard). You can specify the default newline indicator by adding    (the Unix standard). You can specify the default newline indicator by adding
165    --newline-is-cr or --newline-is-lf or --newline-is-crlf or --newline-is-any    --newline-is-cr or --newline-is-lf or --newline-is-crlf or --newline-is-any
166    to the "configure" command, respectively.    to the "configure" command, respectively.
167    
168    If you specify --newline-is-cr or --newline-is-crlf, some of the standard    If you specify --newline-is-cr or --newline-is-crlf, some of the standard
169    tests will fail, because the lines in the test files end with LF. Even if    tests will fail, because the lines in the test files end with LF. Even if
170    the files are edited to change the line endings, there are likely to be some    the files are edited to change the line endings, there are likely to be some
171    failures. With --newline-is-any, many tests should succeed, but there may be    failures. With --newline-is-any, many tests should succeed, but there may be
172    some failures.    some failures.
# Line 194  library. You can read more about them in Line 220  library. You can read more about them in
220    pcre_exec() function; it does not apply to pcre_dfa_exec(), which does not    pcre_exec() function; it does not apply to pcre_dfa_exec(), which does not
221    use deeply nested recursion.    use deeply nested recursion.
222    
223  The "configure" script builds eight files for the basic C library:  The "configure" script builds the following files for the basic C library:
224    
225  . Makefile is the makefile that builds the library  . Makefile is the makefile that builds the library
226  . config.h contains build-time configuration options for the library  . config.h contains build-time configuration options for the library
227    . pcre.h is the public PCRE header file
228  . pcre-config is a script that shows the settings of "configure" options  . pcre-config is a script that shows the settings of "configure" options
229  . libpcre.pc is data for the pkg-config command  . libpcre.pc is data for the pkg-config command
230  . libtool is a script that builds shared and/or static libraries  . libtool is a script that builds shared and/or static libraries
231  . RunTest is a script for running tests on the library  . RunTest is a script for running tests on the basic C library
232  . RunGrepTest is a script for running tests on the pcregrep command  . RunGrepTest is a script for running tests on the pcregrep command
233    
234  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. These are
235    provided for the benefit of those who have to compile PCRE without the benefit
236    of "configure". If you use "configure", the distributed copies are replaced.
237    
238    If a C++ compiler is found, the following files are also built:
239    
240  . pcrecpp.h is the header file for programs that call PCRE via the C++ wrapper  . libpcrecpp.pc is data for the pkg-config command
241    . pcrecpparg.h is a header file for programs that call PCRE via the C++ wrapper
242  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions
243    
244  The "configure" script also creates config.status, which is an executable  The "configure" script also creates config.status, which is an executable
# Line 214  script that can be run to recreate the c Line 246  script that can be run to recreate the c
246  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
247    
248  Once "configure" has run, you can run "make". It builds two libraries, called  Once "configure" has run, you can run "make". It builds two libraries, called
249  libpcre and libpcreposix, a test program called pcretest, and the pcregrep  libpcre and libpcreposix, a test program called pcretest, a demonstration
250  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
251  wrapper library, which is called libpcrecpp, and some test programs called  on your system, it also builds the C++ wrapper library, which is called
252  pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.  libpcrecpp, and some test programs called pcrecpp_unittest,
253    pcre_scanner_unittest, and pcre_stringpiece_unittest.
254  The command "make test" runs all the appropriate tests. Details of the PCRE  
255  tests are given in a separate section of this document, below.  The command "make check" runs all the appropriate tests. Details of the PCRE
256    tests are given below in a separate section of this document.
257  You can use "make install" to copy the libraries, the public header files  
258  pcre.h, pcreposix.h, pcrecpp.h, and pcre_stringpiece.h (the last two only if  You can use "make install" to install PCRE into live directories on your
259  the C++ wrapper was built), and the man pages to appropriate live directories  system. The following are installed (file names are all relative to the
260  on your system, in the normal way.  <prefix> that is set when "configure" is run):
261    
262      Commands (bin):
263        pcretest
264        pcregrep
265        pcre-config
266    
267      Libraries (lib):
268        libpcre
269        libpcreposix
270        libpcrecpp (if C++ support is enabled)
271    
272      Configuration information (lib/pkgconfig):
273        libpcre.pc
274        libpcrecpp.ps (if C++ support is enabled)
275    
276      Header files (include):
277        pcre.h
278        pcreposix.h
279        pcre_scanner.h      )
280        pcre_stringpiece.h  ) if C++ support is enabled
281        pcrecpp.h           )
282        pcrecpparg.h        )
283    
284      Man pages (share/man/man{1,3}):
285        pcregrep.1
286        pcretest.1
287        pcre.3
288        pcre*.3 (lots more pages, all starting "pcre")
289    
290      HTML documentation (share/doc/pcre/html):
291        index.html
292        *.html (lots more pages, hyperlinked from index.html)
293    
294      Text file documentation (share/doc/pcre):
295        AUTHORS
296        COPYING
297        ChangeLog
298        INSTALL
299        LICENCE
300        NON-UNIX-USE
301        NEWS
302        README
303        pcre.txt       (a concatenation of the man(3) pages)
304        pcretest.txt   the pcretest man page
305        pcregrep.txt   the pcregrep man page
306        perltest.txt   some information about the perltest.pl script
307    
308    Note that the pcredemo program that is built by "configure" is *not* installed
309    anywhere. It is a demonstration for programmers wanting to use PCRE.
310    
311  If you want to remove PCRE from your system, you can run "make uninstall".  If you want to remove PCRE from your system, you can run "make uninstall".
312  This removes all the files that "make install" installed. However, it does not  This removes all the files that "make install" installed. However, it does not
313  remove any directories, because these are often shared with other programs.  remove any directories, because these are often shared with other programs.
314    
315    
316  Retrieving configuration information on Unix-like systems  Retrieving configuration information on a Unix-like system
317  ---------------------------------------------------------  ----------------------------------------------------------
318    
319  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
320  to recall information about the PCRE configuration and installation. For  recall information about the PCRE configuration and installation. For example:
 example:  
321    
322    pcre-config --version    pcre-config --version
323    
# Line 256  single command is used. For example: Line 336  single command is used. For example:
336    pkg-config --cflags pcre    pkg-config --cflags pcre
337    
338  The data is held in *.pc files that are installed in a directory called  The data is held in *.pc files that are installed in a directory called
339  pkgconfig.  <prefix>/lib/pkgconfig.
340    
341    
342  Shared libraries on Unix-like systems  Shared libraries on Unix-like systems
# Line 322  To test PCRE on a Unix system, run the R Line 402  To test PCRE on a Unix system, run the R
402  configuring process. There is also a script called RunGrepTest that tests the  configuring process. There is also a script called RunGrepTest that tests the
403  options of the pcregrep command. If the C++ wrapper library is build, three  options of the pcregrep command. If the C++ wrapper library is build, three
404  test programs called pcrecpp_unittest, pcre_scanner_unittest, and  test programs called pcrecpp_unittest, pcre_scanner_unittest, and
405  pcre_stringpiece_unittest are provided.  pcre_stringpiece_unittest are also built.
406    
407  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
408  "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.  
409    
410  The RunTest script runs the pcretest test program (which is documented in its  The RunTest script runs the pcretest test program (which is documented in its
411  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
# Line 337  the test files, give its number as an ar Line 416  the test files, give its number as an ar
416    
417    RunTest 2    RunTest 2
418    
419  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
420  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
421  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
422    version.
423    
424  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),
425  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
# Line 412  re-generated. Line 492  re-generated.
492  The first two 256-byte tables provide lower casing and case flipping functions,  The first two 256-byte tables provide lower casing and case flipping functions,
493  respectively. The next table consists of three 32-byte bit maps which identify  respectively. The next table consists of three 32-byte bit maps which identify
494  digits, "word" characters, and white space, respectively. These are used when  digits, "word" characters, and white space, respectively. These are used when
495  building 32-byte bit maps that represent character classes.  building 32-byte bit maps that represent character classes for code points less
496    than 256.
497    
498  The final 256-byte table has bits indicating various character types, as  The final 256-byte table has bits indicating various character types, as
499  follows:  follows:
# Line 428  You should not alter the set of characte Line 509  You should not alter the set of characte
509  will cause PCRE to malfunction.  will cause PCRE to malfunction.
510    
511    
512  Manifest  File manifest
513  --------  -------------
514    
515  The distribution should contain the following files:  The distribution should contain the following files:
516    
517  (A) The actual source files of the PCRE library functions and their  (A) Source files of the PCRE library functions and their headers:
     headers:  
518    
519    dftables.c            auxiliary program for building chartables.c    dftables.c             auxiliary program for building chartables.c
520    
521      pcreposix.c            )
522      pcre_compile.c         )
523      pcre_config.c          )
524      pcre_dfa_exec.c        )
525      pcre_exec.c            )
526      pcre_fullinfo.c        )
527      pcre_get.c             ) sources for the functions in the library,
528      pcre_globals.c         )   and some internal functions that they use
529      pcre_info.c            )
530      pcre_maketables.c      )
531      pcre_newline.c         )
532      pcre_ord2utf8.c        )
533      pcre_refcount.c        )
534      pcre_study.c           )
535      pcre_tables.c          )
536      pcre_try_flipped.c     )
537      pcre_ucp_searchfuncs.c )
538      pcre_valid_utf8.c      )
539      pcre_version.c         )
540      pcre_xclass.c          )
541      pcre_printint.src      ) debugging function that is #included in pcretest,
542                             )   and can also be #included in pcre_compile()
543      pcre.h                 ) a version of the public PCRE header file
544                             )   for use in non-"configure" environments
545      pcre.h.in              template for pcre.h when built by "configure"
546      pcreposix.h            header for the external POSIX wrapper API
547      pcre_internal.h        header for internal use
548      ucp.h                  ) headers concerned with
549      ucpinternal.h          )   Unicode property handling
550      ucptable.h             ) (this one is the data table)
551    
552      config.h               ) a version of config.h for use in non-"configure"
553                             )   environments
554      config.h.in            template for config.h when built by "configure"
555    
556      pcrecpp.h              public header file for the C++ wrapper
557      pcrecpparg.h.in        template for another C++ header file
558      pcre_scanner.h         public header file for C++ scanner functions
559      pcrecpp.cc             )
560      pcre_scanner.cc        ) source for the C++ wrapper library
561    
562      pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the
563                               C++ stringpiece functions
564      pcre_stringpiece.cc    source for the C++ stringpiece functions
565    
566    (B) Source files for programs that use PCRE:
567    
568    pcreposix.c           )    pcredemo.c             simple demonstration of coding calls to PCRE
569    pcre_compile.c        )    pcregrep.c             source of a grep utility that uses PCRE
570    pcre_config.c         )    pcretest.c             comprehensive test program
571    pcre_dfa_exec.c       )  
572    pcre_exec.c           )  (C) Auxiliary files:
573    pcre_fullinfo.c       )  
574    pcre_get.c            ) sources for the functions in the library,    AUTHORS                information about the author of PCRE
575    pcre_globals.c        )   and some internal functions that they use    ChangeLog              log of changes to the code
576    pcre_info.c           )    INSTALL                generic installation instructions
577    pcre_maketables.c     )    LICENCE                conditions for the use of PCRE
578    pcre_newline.c        )    COPYING                the same, using GNU's standard name
579    pcre_ord2utf8.c       )    Makefile.in            ) template for Unix Makefile, which is built by
580    pcre_refcount.c       )                           )   "configure"
581    pcre_study.c          )    Makefile.am            ) the automake input that was used to create
582    pcre_tables.c         )                           )   Makefile.in
583    pcre_try_flipped.c    )    NEWS                   important changes in this release
584    pcre_ucp_searchfuncs.c)    NON-UNIX-USE           notes on building PCRE on non-Unix systems
585    pcre_valid_utf8.c     )    README                 this file
586    pcre_version.c        )    RunTest.in             template for a Unix shell script for running tests
587    pcre_xclass.c         )    RunGrepTest.in         template for a Unix shell script for pcregrep tests
588      aclocal.m4             m4 macros (generated by "aclocal")
589    pcre_printint.src     ) debugging function that is #included in pcretest, and    config.guess           ) files used by libtool,
590                          )   can also be #included in pcre_compile()    config.sub             )   used only when building a shared library
591      configure              a configuring shell script (built by autoconf)
592    pcre.h                the public PCRE header file    configure.ac           ) the autoconf input that was used to build
593    pcreposix.h           header for the external POSIX wrapper API                           )   "configure" and config.h
594    pcre_internal.h       header for internal use    depcomp                ) script to find program dependencies, generated by
595    ucp.h                 ) headers concerned with                           )   automake
596    ucpinternal.h         )   Unicode property handling    doc/*.3                man page sources for the PCRE functions
597    ucptable.h            ) (this one is the data table)    doc/*.1                man page sources for pcregrep and pcretest
598    config.in             template for config.h, which is built by configure    doc/html/*             HTML documentation
599      doc/pcre.txt           plain text version of the man pages
600    pcrecpp.h             the header file for the C++ wrapper    doc/pcretest.txt       plain text documentation of test program
601    pcrecpparg.h.in       "source" for another C++ header file    doc/perltest.txt       plain text documentation of Perl test program
602    pcrecpp.cc            )    install-sh             a shell script for installing files
603    pcre_scanner.cc       ) source for the C++ wrapper library    libpcre.pc.in          template for libpcre.pc for pkg-config
604      libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config
605    pcre_stringpiece.h.in "source" for pcre_stringpiece.h, the header for the    ltmain.sh              file used to build a libtool script
606                            C++ stringpiece functions    missing                ) common stub for a few missing GNU programs while
607    pcre_stringpiece.cc   source for the C++ stringpiece functions                           )   installing, generated by automake
608      mkinstalldirs          script for making install directories
609  (B) Auxiliary files:    perltest.pl            Perl test program
610      pcre-config.in         source of script which retains PCRE information
   AUTHORS               information about the author of PCRE  
   ChangeLog             log of changes to the code  
   INSTALL               generic installation instructions  
   LICENCE               conditions for the use of PCRE  
   COPYING               the same, using GNU's standard name  
   Makefile.in           template for Unix Makefile, which is built by configure  
   NEWS                  important changes in this release  
   NON-UNIX-USE          notes on building PCRE on non-Unix systems  
   README                this file  
   RunTest.in            template for a Unix shell script for running tests  
   RunGrepTest.in        template for a Unix shell script for pcregrep tests  
   config.guess          ) files used by libtool,  
   config.sub            )   used only when building a shared library  
   config.h.in           "source" for the config.h header file  
   configure             a configuring shell script (built by autoconf)  
   configure.ac          the autoconf input used to build configure  
   doc/Tech.Notes        notes on the encoding  
   doc/*.3               man page sources for the PCRE functions  
   doc/*.1               man page sources for pcregrep and pcretest  
   doc/html/*            HTML documentation  
   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         "source" for libpcre.pc for pkg-config  
   ltmain.sh             file used to build a libtool script  
   mkinstalldirs         script for making install directories  
   pcretest.c            comprehensive test program  
   pcredemo.c            simple demonstration of coding calls to PCRE  
   perltest.pl           Perl test program  
   pcregrep.c            source of a grep utility that uses PCRE  
   pcre-config.in        source of script which retains PCRE information  
611    pcrecpp_unittest.c           )    pcrecpp_unittest.c           )
612    pcre_scanner_unittest.c      ) test programs for the C++ wrapper    pcre_scanner_unittest.c      ) test programs for the C++ wrapper
613    pcre_stringpiece_unittest.c  )    pcre_stringpiece_unittest.c  )
614    testdata/testinput*   test data for main library tests    testdata/testinput*    test data for main library tests
615    testdata/testoutput*  expected test results    testdata/testoutput*   expected test results
616    testdata/grep*        input and output for pcregrep tests    testdata/grep*         input and output for pcregrep tests
617    
618  (C) Auxiliary files for Win32 DLL  (D) Auxiliary files for cmake support
619    
620    libpcre.def    CMakeLists.txt
621    libpcreposix.def    config-cmake.h.in
622    
623  (D) Auxiliary file for VPASCAL  (E) Auxiliary files for VPASCAL
624    
625    makevp.bat    makevp.bat
626      !compile.txt
627      !linklib.txt
628      pcregexp.pas
629    
630    (F) Miscellaneous
631    
632      RunTest.bat            a script for running tests under Windows
633    
634  Philip Hazel  Philip Hazel
635  Email local part: ph10  Email local part: ph10
636  Email domain: cam.ac.uk  Email domain: cam.ac.uk
637  March 2007  Last updated: March 2007

Legend:
Removed from v.101  
changed lines
  Added in v.109

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12