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

Diff of /code/trunk/README

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

revision 123 by ph10, Mon Mar 12 15:19:06 2007 UTC revision 391 by ph10, Tue Mar 17 21:16:01 2009 UTC
# Line 1  Line 1 
1  README file for PCRE (Perl-compatible regular expression library)  README file for PCRE (Perl-compatible regular expression library)
2  -----------------------------------------------------------------  -----------------------------------------------------------------
3    
4  The latest release of PCRE is always available from  The latest release of PCRE is always available in three alternative formats
5    from:
6    
7    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
8      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.bz2
9      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.zip
10    
11  There is a mailing list for discussion about the development of PCRE at  There is a mailing list for discussion about the development of PCRE at
12    
# Line 30  The contents of this README file are: Line 33  The contents of this README file are:
33  The PCRE APIs  The PCRE APIs
34  -------------  -------------
35    
36  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
37  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
38  for details).  of Google Inc.
39    
40  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
41  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
42  that this just provides a POSIX calling interface to PCRE; the regular  library called libpcreposix. Note that this just provides a POSIX calling
43  expressions themselves still follow Perl syntax and semantics. The POSIX API is  interface to PCRE; the regular expressions themselves still follow Perl syntax
44  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
45    all of PCRE's facilities.
46    
47  The header file for the POSIX-style functions is called pcreposix.h. The  The header file for the POSIX-style functions is called pcreposix.h. The
48  official POSIX name is regex.h, but I did not want to risk possible problems  official POSIX name is regex.h, but I did not want to risk possible problems
# Line 91  You can find contributions from PCRE use Line 95  You can find contributions from PCRE use
95    
96  There is a README file giving brief descriptions of what they are. Some are  There is a README file giving brief descriptions of what they are. Some are
97  complete in themselves; others are pointers to URLs containing relevant files.  complete in themselves; others are pointers to URLs containing relevant files.
98  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
99  of the contributions provide support for compiling PCRE on various flavours of  contributions provided support for compiling PCRE on various flavours of
100  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
101  support in the standard distribution.  in the standard distribution, so these contibutions have been archived.
102    
103    
104  Building PCRE on non-Unix systems  Building PCRE on non-Unix systems
# Line 102  Building PCRE on non-Unix systems Line 106  Building PCRE on non-Unix systems
106    
107  For a non-Unix system, please read the comments in the file NON-UNIX-USE,  For a non-Unix system, please read the comments in the file NON-UNIX-USE,
108  though if your system supports the use of "configure" and "make" you may be  though if your system supports the use of "configure" and "make" you may be
109  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
110    configured in many platform environments using the GUI facility of CMake's
111    CMakeSetup. It creates Makefiles, solution files, etc.
112    
113  PCRE has been compiled on many different operating systems. It should be  PCRE has been compiled on many different operating systems. It should be
114  straightforward to build PCRE on any system that has a Standard C compiler and  straightforward to build PCRE on any system that has a Standard C compiler and
# Line 115  Building PCRE on Unix-like systems Line 121  Building PCRE on Unix-like systems
121  If you are using HP's ANSI C++ compiler (aCC), please see the special note  If you are using HP's ANSI C++ compiler (aCC), please see the special note
122  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
123    
124    The following instructions assume the use of the widely used "configure, make,
125    make install" process. There is also support for CMake in the PCRE
126    distribution; there are some comments about using CMake in the NON-UNIX-USE
127    file, though it can also be used in Unix-like systems.
128    
129  To build PCRE on a Unix-like system, first run the "configure" command from the  To build PCRE on a Unix-like system, first run the "configure" command from the
130  PCRE distribution directory, with your current directory set to the directory  PCRE distribution directory, with your current directory set to the directory
131  where you want the files to be created. This command is a standard GNU  where you want the files to be created. This command is a standard GNU
# Line 147  library. You can read more about them in Line 158  library. You can read more about them in
158    
159  . If you want to suppress the building of the C++ wrapper library, you can add  . If you want to suppress the building of the C++ wrapper library, you can add
160    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,
161    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,
162    will try to build the C++ wrapper.    it will try to build the C++ wrapper.
163    
164  . 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
165    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
166    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,
167    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
168      with this option, its input can only either be ASCII or UTF-8, even when
169      running on EBCDIC platforms. It is not possible to use both --enable-utf8 and
170      --enable-ebcdic at the same time.
171    
172  . If, in addition to support for UTF-8 character strings, you want to include  . If, in addition to support for UTF-8 character strings, you want to include
173    support for the \P, \p, and \X sequences that recognize Unicode character    support for the \P, \p, and \X sequences that recognize Unicode character
# Line 163  library. You can read more about them in Line 177  library. You can read more about them in
177    supported.    supported.
178    
179  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any
180    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
181    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
182    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
183    (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
184    --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
185    to the "configure" command, respectively.    or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
186      --enable-newline-is-any to the "configure" command, respectively.
187    If you specify --newline-is-cr or --newline-is-crlf, some of the standard  
188    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
189    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
190    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
191    some failures.    to be some failures. With --enable-newline-is-anycrlf or
192      --enable-newline-is-any, many tests should succeed, but there may be some
193      failures.
194    
195    . By default, the sequence \R in a pattern matches any Unicode line ending
196      sequence. This is independent of the option specifying what PCRE considers to
197      be the end of a line (see above). However, the caller of PCRE can restrict \R
198      to match only CR, LF, or CRLF. You can make this the default by adding
199      --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
200    
201  . When called via the POSIX interface, PCRE uses malloc() to get additional  . When called via the POSIX interface, PCRE uses malloc() to get additional
202    storage for processing capturing parentheses if there are more than 10 of    storage for processing capturing parentheses if there are more than 10 of
203    them. You can increase this threshold by setting, for example,    them in a pattern. You can increase this threshold by setting, for example,
204    
205    --with-posix-malloc-threshold=20    --with-posix-malloc-threshold=20
206    
# Line 207  library. You can read more about them in Line 229  library. You can read more about them in
229  . The default maximum compiled pattern size is around 64K. You can increase  . The default maximum compiled pattern size is around 64K. You can increase
230    this by adding --with-link-size=3 to the "configure" command. You can    this by adding --with-link-size=3 to the "configure" command. You can
231    increase it even more by setting --with-link-size=4, but this is unlikely    increase it even more by setting --with-link-size=4, but this is unlikely
232    ever to be necessary.    ever to be necessary. Increasing the internal link size will reduce
233      performance.
234    
235  . You can build PCRE so that its internal match() function that is called from  . You can build PCRE so that its internal match() function that is called from
236    pcre_exec() does not call itself recursively. Instead, it uses memory blocks    pcre_exec() does not call itself recursively. Instead, it uses memory blocks
# Line 223  library. You can read more about them in Line 246  library. You can read more about them in
246    use deeply nested recursion. There is a discussion about stack sizes in the    use deeply nested recursion. There is a discussion about stack sizes in the
247    pcrestack man page.    pcrestack man page.
248    
249    . For speed, PCRE uses four tables for manipulating and identifying characters
250      whose code point values are less than 256. By default, it uses a set of
251      tables for ASCII encoding that is part of the distribution. If you specify
252    
253      --enable-rebuild-chartables
254    
255      a program called dftables is compiled and run in the default C locale when
256      you obey "make". It builds a source file called pcre_chartables.c. If you do
257      not specify this option, pcre_chartables.c is created as a copy of
258      pcre_chartables.c.dist. See "Character tables" below for further information.
259    
260    . It is possible to compile PCRE for use on systems that use EBCDIC as their
261      character code (as opposed to ASCII) by specifying
262    
263      --enable-ebcdic
264    
265      This automatically implies --enable-rebuild-chartables (see above). However,
266      when PCRE is built this way, it always operates in EBCDIC. It cannot support
267      both EBCDIC and UTF-8.
268    
269    . It is possible to compile pcregrep to use libz and/or libbz2, in order to
270      read .gz and .bz2 files (respectively), by specifying one or both of
271    
272      --enable-pcregrep-libz
273      --enable-pcregrep-libbz2
274    
275      Of course, the relevant libraries must be installed on your system.
276    
277    . It is possible to compile pcretest so that it links with the libreadline
278      library, by specifying
279    
280      --enable-pcretest-libreadline
281    
282      If this is done, when pcretest's input is from a terminal, it reads it using
283      the readline() function. This provides line-editing and history facilities.
284      Note that libreadline is GPL-licenced, so if you distribute a binary of
285      pcretest linked in this way, there may be licensing issues.
286    
287      Setting this option causes the -lreadline option to be added to the pcretest
288      build. In many operating environments with a sytem-installed readline
289      library this is sufficient. However, in some environments (e.g. if an
290      unmodified distribution version of readline is in use), it may be necessary
291      to specify something like LIBS="-lncurses" as well. This is because, to quote
292      the readline INSTALL, "Readline uses the termcap functions, but does not link
293      with the termcap or curses library itself, allowing applications which link
294      with readline the to choose an appropriate library." If you get error
295      messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,
296      this is the problem, and linking with the ncurses library should fix it.
297    
298  The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
299    
300  . Makefile is the makefile that builds the library  . Makefile is the makefile that builds the library
# Line 250  script that can be run to recreate the c Line 322  script that can be run to recreate the c
322  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
323    
324  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
325  libpcre and libpcreposix, a test program called pcretest, a demonstration  libpcre and libpcreposix, a test program called pcretest, and the pcregrep
326  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++
327  on your system, "make" also builds the C++ wrapper library, which is called  wrapper library, which is called libpcrecpp, and some test programs called
328  libpcrecpp, and some test programs called pcrecpp_unittest,  pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
329  pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper  Building the C++ wrapper can be disabled by adding --disable-cpp to the
330  can be disabled by adding --disable-cpp to the "configure" command.  "configure" command.
331    
332  The command "make check" runs all the appropriate tests. Details of the PCRE  The command "make check" runs all the appropriate tests. Details of the PCRE
333  tests are given below in a separate section of this document.  tests are given below in a separate section of this document.
# Line 307  system. The following are installed (fil Line 379  system. The following are installed (fil
379      pcretest.txt   the pcretest man page      pcretest.txt   the pcretest man page
380      pcregrep.txt   the pcregrep man page      pcregrep.txt   the pcregrep man page
381    
 Note that the pcredemo program that is built by "configure" is *not* installed  
 anywhere. It is a demonstration for programmers wanting to use PCRE.  
   
382  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".
383  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
384  remove any directories, because these are often shared with other programs.  remove any directories, because these are often shared with other programs.
# Line 371  Cross-compiling on Unix-like systems Line 440  Cross-compiling on Unix-like systems
440  ------------------------------------  ------------------------------------
441    
442  You can specify CC and CFLAGS in the normal way to the "configure" command, in  You can specify CC and CFLAGS in the normal way to the "configure" command, in
443  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
444  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
445  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
446  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,
447  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
448  there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)  compiler.
449  when calling the "configure" command. If they are not specified, they default  
450  to the values of CC and CFLAGS.  When --enable-rebuild-chartables is not specified, pcre_chartables.c is created
451    by making a copy of pcre_chartables.c.dist, which is a default set of tables
452    that assumes ASCII code. Cross-compiling with the default tables should not be
453    a problem.
454    
455    If you need to modify the character tables when cross-compiling, you should
456    move pcre_chartables.c.dist out of the way, then compile dftables.c by hand and
457    run it on the local host to make a new version of pcre_chartables.c.dist.
458    Then when you cross-compile PCRE this new version of the tables will be used.
459    
460    
461  Using HP's ANSI C++ compiler (aCC)  Using HP's ANSI C++ compiler (aCC)
# Line 401  Making new tarballs Line 478  Making new tarballs
478  -------------------  -------------------
479    
480  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
481  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
482  doc directory, you should first run the PrepareRelease script. This re-creates  build of the new distribution to ensure that it works.
483  the .txt and HTML forms of the documentation from the man pages.  
484    If you have modified any of the man page sources in the doc directory, you
485    should first run the PrepareRelease script before making a distribution. This
486    script creates the .txt and HTML forms of the documentation from the man pages.
487    
488    
489  Testing PCRE  Testing PCRE
# Line 461  is output to say why. If running this te Line 541  is output to say why. If running this te
541  in the comparison output, it means that locale is not available on your system,  in the comparison output, it means that locale is not available on your system,
542  despite being listed by "locale". This does not mean that PCRE is broken.  despite being listed by "locale". This does not mean that PCRE is broken.
543    
544    [If you are trying to run this test on Windows, you may be able to get it to
545    work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
546    RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
547    Windows versions of test 2. More info on using RunTest.bat is included in the
548    document entitled NON-UNIX-USE.]
549    
550  The fourth test checks the UTF-8 support. It is not run automatically unless  The fourth test checks the UTF-8 support. It is not run automatically unless
551  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when
552  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 script,
# Line 490  concatenated tables. A call to pcre_make Line 576  concatenated tables. A call to pcre_make
576  of tables in the current locale. If the final argument for pcre_compile() is  of tables in the current locale. If the final argument for pcre_compile() is
577  passed as NULL, a set of 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.
578    
579  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
580  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
581  (compiled from dftables.c), which uses the ANSI C character handling functions  tables for ASCII coding. However, if --enable-rebuild-chartables is specified
582  such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table  for ./configure, a different version of pcre_chartables.c is built by the
583  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
584  control the contents of these default tables. You can change the default tables  handling functions such as isalnum(), isalpha(), isupper(), islower(), etc. to
585  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
586  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
587    the default tables by editing pcre_chartables.c and then re-building PCRE. If
588    you do this, you should take care to ensure that the file does not get
589    automatically re-generated. The best way to do this is to move
590    pcre_chartables.c.dist out of the way and replace it with your customized
591    tables.
592    
593    When the dftables program is run as a result of --enable-rebuild-chartables,
594    it uses the default C locale that is set on your system. It does not pay
595    attention to the LC_xxx environment variables. In other words, it uses the
596    system's default locale rather than whatever the compiling user happens to have
597    set. If you really do want to build a source set of character tables in a
598    locale that is specified by the LC_xxx variables, you can run the dftables
599    program by hand with the -L option. For example:
600    
601      ./dftables -L pcre_chartables.c.special
602    
603  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,
604  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
# Line 526  The distribution should contain the foll Line 627  The distribution should contain the foll
627    
628  (A) Source files of the PCRE library functions and their headers:  (A) Source files of the PCRE library functions and their headers:
629    
630    dftables.c             auxiliary program for building chartables.c    dftables.c              auxiliary program for building pcre_chartables.c
631                                when --enable-rebuild-chartables is specified
632    
633    pcreposix.c            )    pcre_chartables.c.dist  a default set of character tables that assume ASCII
634    pcre_compile.c         )                              coding; used, unless --enable-rebuild-chartables is
635    pcre_config.c          )                              specified, by copying to pcre_chartables.c
636    pcre_dfa_exec.c        )  
637    pcre_exec.c            )    pcreposix.c             )
638    pcre_fullinfo.c        )    pcre_compile.c          )
639    pcre_get.c             ) sources for the functions in the library,    pcre_config.c           )
640    pcre_globals.c         )   and some internal functions that they use    pcre_dfa_exec.c         )
641    pcre_info.c            )    pcre_exec.c             )
642    pcre_maketables.c      )    pcre_fullinfo.c         )
643    pcre_newline.c         )    pcre_get.c              ) sources for the functions in the library,
644    pcre_ord2utf8.c        )    pcre_globals.c          )   and some internal functions that they use
645    pcre_refcount.c        )    pcre_info.c             )
646    pcre_study.c           )    pcre_maketables.c       )
647    pcre_tables.c          )    pcre_newline.c          )
648    pcre_try_flipped.c     )    pcre_ord2utf8.c         )
649    pcre_ucp_searchfuncs.c )    pcre_refcount.c         )
650    pcre_valid_utf8.c      )    pcre_study.c            )
651    pcre_version.c         )    pcre_tables.c           )
652    pcre_xclass.c          )    pcre_try_flipped.c      )
653    pcre_printint.src      ) debugging function that is #included in pcretest,    pcre_ucd.c              )
654                           )   and can also be #included in pcre_compile()    pcre_valid_utf8.c       )
655    pcre.h.in              template for pcre.h when built by "configure"    pcre_version.c          )
656    pcreposix.h            header for the external POSIX wrapper API    pcre_xclass.c           )
657    pcre_internal.h        header for internal use    pcre_printint.src       ) debugging function that is #included in pcretest,
658    ucp.h                  ) headers concerned with                            )   and can also be #included in pcre_compile()
659    ucpinternal.h          )   Unicode property handling    pcre.h.in               template for pcre.h when built by "configure"
660    ucptable.h             ) (this one is the data table)    pcreposix.h             header for the external POSIX wrapper API
661      pcre_internal.h         header for internal use
662    config.h.in            template for config.h, which is built by "configure"    ucp.h                   header for Unicode property handling
663    
664    pcrecpp.h              public header file for the C++ wrapper    config.h.in             template for config.h, which is built by "configure"
665    pcrecpparg.h.in        template for another C++ header file  
666    pcre_scanner.h         public header file for C++ scanner functions    pcrecpp.h               public header file for the C++ wrapper
667    pcrecpp.cc             )    pcrecpparg.h.in         template for another C++ header file
668    pcre_scanner.cc        ) source for the C++ wrapper library    pcre_scanner.h          public header file for C++ scanner functions
669      pcrecpp.cc              )
670    pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the    pcre_scanner.cc         ) source for the C++ wrapper library
671                             C++ stringpiece functions  
672    pcre_stringpiece.cc    source for the C++ stringpiece functions    pcre_stringpiece.h.in   template for pcre_stringpiece.h, the header for the
673                                C++ stringpiece functions
674      pcre_stringpiece.cc     source for the C++ stringpiece functions
675    
676  (B) Source files for programs that use PCRE:  (B) Source files for programs that use PCRE:
677    
678    pcredemo.c             simple demonstration of coding calls to PCRE    pcredemo.c              simple demonstration of coding calls to PCRE
679    pcregrep.c             source of a grep utility that uses PCRE    pcregrep.c              source of a grep utility that uses PCRE
680    pcretest.c             comprehensive test program    pcretest.c              comprehensive test program
681    
682  (C) Auxiliary files:  (C) Auxiliary files:
683    
684    132html                script to turn "man" pages into HTML    132html                 script to turn "man" pages into HTML
685    AUTHORS                information about the author of PCRE    AUTHORS                 information about the author of PCRE
686    ChangeLog              log of changes to the code    ChangeLog               log of changes to the code
687    CleanTxt               script to clean nroff output for txt man pages    CleanTxt                script to clean nroff output for txt man pages
688    Detrail                script to remove trailing spaces    Detrail                 script to remove trailing spaces
689    Index.html             the base HTML page    HACKING                 some notes about the internals of PCRE
690    INSTALL                generic installation instructions    INSTALL                 generic installation instructions
691    LICENCE                conditions for the use of PCRE    LICENCE                 conditions for the use of PCRE
692    COPYING                the same, using GNU's standard name    COPYING                 the same, using GNU's standard name
693    Makefile.in            ) template for Unix Makefile, which is built by    Makefile.in             ) template for Unix Makefile, which is built by
694                           )   "configure"                            )   "configure"
695    Makefile.am            ) the automake input that was used to create    Makefile.am             ) the automake input that was used to create
696                           )   Makefile.in                            )   Makefile.in
697    NEWS                   important changes in this release    NEWS                    important changes in this release
698    NON-UNIX-USE           notes on building PCRE on non-Unix systems    NON-UNIX-USE            notes on building PCRE on non-Unix systems
699    PrepareRelease         script to make preparations for "make dist"    PrepareRelease          script to make preparations for "make dist"
700    README                 this file    README                  this file
701    RunTest.in             template for a Unix shell script for running tests    RunTest                 a Unix shell script for running tests
702    RunGrepTest.in         template for a Unix shell script for pcregrep tests    RunGrepTest             a Unix shell script for pcregrep tests
703    aclocal.m4             m4 macros (generated by "aclocal")    aclocal.m4              m4 macros (generated by "aclocal")
704    config.guess           ) files used by libtool,    config.guess            ) files used by libtool,
705    config.sub             )   used only when building a shared library    config.sub              )   used only when building a shared library
706    configure              a configuring shell script (built by autoconf)    configure               a configuring shell script (built by autoconf)
707    configure.ac           ) the autoconf input that was used to build    configure.ac            ) the autoconf input that was used to build
708                           )   "configure" and config.h                            )   "configure" and config.h
709    depcomp                ) script to find program dependencies, generated by    depcomp                 ) script to find program dependencies, generated by
710                           )   automake                            )   automake
711    doc/*.3                man page sources for the PCRE functions    doc/*.3                 man page sources for the PCRE functions
712    doc/*.1                man page sources for pcregrep and pcretest    doc/*.1                 man page sources for pcregrep and pcretest
713    doc/html/*             HTML documentation    doc/index.html.src      the base HTML page
714    doc/pcre.txt           plain text version of the man pages    doc/html/*              HTML documentation
715    doc/pcretest.txt       plain text documentation of test program    doc/pcre.txt            plain text version of the man pages
716    doc/perltest.txt       plain text documentation of Perl test program    doc/pcretest.txt        plain text documentation of test program
717    install-sh             a shell script for installing files    doc/perltest.txt        plain text documentation of Perl test program
718    libpcre.pc.in          template for libpcre.pc for pkg-config    install-sh              a shell script for installing files
719    libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config    libpcre.pc.in           template for libpcre.pc for pkg-config
720    ltmain.sh              file used to build a libtool script    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
721    missing                ) common stub for a few missing GNU programs while    ltmain.sh               file used to build a libtool script
722                           )   installing, generated by automake    missing                 ) common stub for a few missing GNU programs while
723    mkinstalldirs          script for making install directories                            )   installing, generated by automake
724    perltest.pl            Perl test program    mkinstalldirs           script for making install directories
725    pcre-config.in         source of script which retains PCRE information    perltest.pl             Perl test program
726      pcre-config.in          source of script which retains PCRE information
727    pcrecpp_unittest.cc          )    pcrecpp_unittest.cc          )
728    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
729    pcre_stringpiece_unittest.cc )    pcre_stringpiece_unittest.cc )
730    testdata/testinput*    test data for main library tests    testdata/testinput*     test data for main library tests
731    testdata/testoutput*   expected test results    testdata/testoutput*    expected test results
732    testdata/grep*         input and output for pcregrep tests    testdata/grep*          input and output for pcregrep tests
733    
734  (D) Auxiliary files for cmake support  (D) Auxiliary files for cmake support
735    
736      cmake/COPYING-CMAKE-SCRIPTS
737      cmake/FindPackageHandleStandardArgs.cmake
738      cmake/FindReadline.cmake
739    CMakeLists.txt    CMakeLists.txt
740    config-cmake.h.in    config-cmake.h.in
741    
742  (E) Auxiliary files for VPASCAL  (E) Auxiliary files for VPASCAL
743    
744    makevp.bat    makevp.bat
745    !compile.txt    makevp_c.txt
746    !linklib.txt    makevp_l.txt
747    pcregexp.pas    pcregexp.pas
748    
749  (F) Auxiliary files for building PCRE "by hand"  (F) Auxiliary files for building PCRE "by hand"
750    
751    pcre.h.generic         ) a version of the public PCRE header file    pcre.h.generic          ) a version of the public PCRE header file
752                           )   for use in non-"configure" environments                            )   for use in non-"configure" environments
753    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"
754                           )   environments                            )   environments
755    
756  (F) Miscellaneous  (F) Miscellaneous
757    
# Line 652  The distribution should contain the foll Line 760  The distribution should contain the foll
760  Philip Hazel  Philip Hazel
761  Email local part: ph10  Email local part: ph10
762  Email domain: cam.ac.uk  Email domain: cam.ac.uk
763  Last updated: March 2007  Last updated: 17 March 2009

Legend:
Removed from v.123  
changed lines
  Added in v.391

  ViewVC Help
Powered by ViewVC 1.1.5