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

Diff of /code/trunk/README

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

revision 53 by nigel, Sat Feb 24 21:39:42 2007 UTC revision 77 by nigel, Sat Feb 24 21:40:45 2007 UTC
# Line 7  The latest release of PCRE is always ava Line 7  The latest release of PCRE is always ava
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    
10  PCRE has its own native API, but a set of "wrapper" functions that are based on  
11  the POSIX API are also supplied in the library libpcreposix. Note that this  The PCRE APIs
12  just provides a POSIX calling interface to PCRE: the regular expressions  -------------
13  themselves still follow Perl syntax and semantics. The header file  
14  for the POSIX-style functions is called pcreposix.h. The official POSIX name is  PCRE is written in C, and it has its own API. The distribution now includes a
15  regex.h, but I didn't want to risk possible problems with existing files of  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page
16  that name by distributing it that way. To use it with an existing program that  for details).
17  uses the POSIX API, it will have to be renamed or pointed at by a link.  
18    Also included are a set of C wrapper functions that are based on the POSIX
19    API. These end up in the library called libpcreposix. Note that this just
20    provides a POSIX calling interface to PCRE: the regular expressions themselves
21    still follow Perl syntax and semantics. The header file for the POSIX-style
22    functions is called pcreposix.h. The official POSIX name is regex.h, but I
23    didn't want to risk possible problems with existing files of that name by
24    distributing it that way. To use it with an existing program that uses the
25    POSIX API, it will have to be renamed or pointed at by a link.
26    
27    If you are using the POSIX interface to PCRE and there is already a POSIX regex
28    library installed on your system, you must take care when linking programs to
29    ensure that they link with PCRE's libpcreposix library. Otherwise they may pick
30    up the "real" POSIX functions of the same name.
31    
32    
33    Documentation for PCRE
34    ----------------------
35    
36    If you install PCRE in the normal way, you will end up with an installed set of
37    man pages whose names all start with "pcre". The one that is called "pcre"
38    lists all the others. In addition to these man pages, the PCRE documentation is
39    supplied in two other forms; however, as there is no standard place to install
40    them, they are left in the doc directory of the unpacked source distribution.
41    These forms are:
42    
43      1. Files called doc/pcre.txt, doc/pcregrep.txt, and doc/pcretest.txt. The
44         first of these is a concatenation of the text forms of all the section 3
45         man pages except those that summarize individual functions. The other two
46         are the text forms of the section 1 man pages for the pcregrep and
47         pcretest commands. Text forms are provided for ease of scanning with text
48         editors or similar tools.
49    
50      2. A subdirectory called doc/html contains all the documentation in HTML
51         form, hyperlinked in various ways, and rooted in a file called
52         doc/index.html.
53    
54    
55  Contributions by users of PCRE  Contributions by users of PCRE
# Line 30  Windows systems (I myself do not use Win Line 65  Windows systems (I myself do not use Win
65  others are pointers to URLs containing relevant files.  others are pointers to URLs containing relevant files.
66    
67    
68  Building PCRE on a Unix system  Building PCRE on a Unix-like system
69  ------------------------------  -----------------------------------
70    
71  To build PCRE on a Unix system, first run the "configure" command from the PCRE  To build PCRE on a Unix-like system, first run the "configure" command from the
72  distribution directory, with your current directory set to the directory where  PCRE distribution directory, with your current directory set to the directory
73  you want the files to be created. This command is a standard GNU "autoconf"  where you want the files to be created. This command is a standard GNU
74  configuration script, for which generic instructions are supplied in INSTALL.  "autoconf" configuration script, for which generic instructions are supplied in
75    INSTALL.
76    
77  Most commonly, people build PCRE within its own distribution directory, and in  Most commonly, people build PCRE within its own distribution directory, and in
78  this case, on many systems, just running "./configure" is sufficient, but the  this case, on many systems, just running "./configure" is sufficient, but the
79  usual methods of changing standard defaults are available. For example,  usual methods of changing standard defaults are available. For example:
80    
81  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
82    
# Line 55  into /source/pcre/pcre-xxx, but you want Line 91  into /source/pcre/pcre-xxx, but you want
91  cd /build/pcre/pcre-xxx  cd /build/pcre/pcre-xxx
92  /source/pcre/pcre-xxx/configure  /source/pcre/pcre-xxx/configure
93    
94  If you want to make use of the experimential, incomplete support for UTF-8  There are some optional features that can be included or omitted from the PCRE
95  character strings in PCRE, you must add --enable-utf8 to the "configure"  library. You can read more about them in the pcrebuild man page.
 command. Without it, the code for handling UTF-8 is not included in the  
 library. (Even when included, it still has to be enabled by an option at run  
 time.)  
   
 The "configure" script builds five files:  
96    
97    . If you want to make use of the support for UTF-8 character strings in PCRE,
98      you must add --enable-utf8 to the "configure" command. Without it, the code
99      for handling UTF-8 is not included in the library. (Even when included, it
100      still has to be enabled by an option at run time.)
101    
102    . If, in addition to support for UTF-8 character strings, you want to include
103      support for the \P, \p, and \X sequences that recognize Unicode character
104      properties, you must add --enable-unicode-properties to the "configure"
105      command. This adds about 90K to the size of the library (in the form of a
106      property table); only the basic two-letter properties such as Lu are
107      supported.
108    
109    . You can build PCRE to recognized CR or NL as the newline character, instead
110      of whatever your compiler uses for "\n", by adding --newline-is-cr or
111      --newline-is-nl to the "configure" command, respectively. Only do this if you
112      really understand what you are doing. On traditional Unix-like systems, the
113      newline character is NL.
114    
115    . When called via the POSIX interface, PCRE uses malloc() to get additional
116      storage for processing capturing parentheses if there are more than 10 of
117      them. You can increase this threshold by setting, for example,
118    
119      --with-posix-malloc-threshold=20
120    
121      on the "configure" command.
122    
123    . PCRE has a counter that can be set to limit the amount of resources it uses.
124      If the limit is exceeded during a match, the match fails. The default is ten
125      million. You can change the default by setting, for example,
126    
127      --with-match-limit=500000
128    
129      on the "configure" command. This is just the default; individual calls to
130      pcre_exec() can supply their own value. There is discussion on the pcreapi
131      man page.
132    
133    . The default maximum compiled pattern size is around 64K. You can increase
134      this by adding --with-link-size=3 to the "configure" command. You can
135      increase it even more by setting --with-link-size=4, but this is unlikely
136      ever to be necessary. If you build PCRE with an increased link size, test 2
137      (and 5 if you are using UTF-8) will fail. Part of the output of these tests
138      is a representation of the compiled pattern, and this changes with the link
139      size.
140    
141    . You can build PCRE so that its internal match() function that is called from
142      pcre_exec() does not call itself recursively. Instead, it uses blocks of data
143      from the heap via special functions pcre_stack_malloc() and pcre_stack_free()
144      to save data that would otherwise be saved on the stack. To build PCRE like
145      this, use
146    
147      --disable-stack-for-recursion
148    
149      on the "configure" command. PCRE runs more slowly in this mode, but it may be
150      necessary in environments with limited stack sizes. This applies only to the
151      pcre_exec() function; it does not apply to pcre_dfa_exec(), which does not
152      use deeply nested recursion.
153    
154    The "configure" script builds eight files for the basic C library:
155    
156    . pcre.h is the header file for C programs that call PCRE
157    . Makefile is the makefile that builds the library
158    . config.h contains build-time configuration options for the library
159    . pcre-config is a script that shows the settings of "configure" options
160    . libpcre.pc is data for the pkg-config command
161  . libtool is a script that builds shared and/or static libraries  . libtool is a script that builds shared and/or static libraries
162  . Makefile is built by copying Makefile.in and making substitutions.  . RunTest is a script for running tests on the library
163  . config.h is built by copying config.in and making substitutions.  . RunGrepTest is a script for running tests on the pcregrep command
 . pcre-config is built by copying pcre-config.in and making substitutions.  
 . RunTest is a script for running tests  
164    
165  Once "configure" has run, you can run "make". It builds two libraries called  In addition, if a C++ compiler is found, the following are also built:
166    
167    . pcrecpp.h is the header file for programs that call PCRE via the C++ wrapper
168    . pcre_stringpiece.h is the header for the C++ "stringpiece" functions
169    
170    The "configure" script also creates config.status, which is an executable
171    script that can be run to recreate the configuration, and config.log, which
172    contains compiler output from tests that "configure" runs.
173    
174    Once "configure" has run, you can run "make". It builds two libraries, called
175  libpcre and libpcreposix, a test program called pcretest, and the pcregrep  libpcre and libpcreposix, a test program called pcretest, and the pcregrep
176  command. You can use "make install" to copy these, the public header files  command. If a C++ compiler was found on your system, it also builds the C++
177  pcre.h and pcreposix.h, and the man pages to appropriate live directories on  wrapper library, which is called libpcrecpp, and some test programs called
178  your system, in the normal way.  pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
179    
180    The command "make test" runs all the appropriate tests. Details of the PCRE
181    tests are given in a separate section of this document, below.
182    
183    You can use "make install" to copy the libraries, the public header files
184    pcre.h, pcreposix.h, pcrecpp.h, and pcre_stringpiece.h (the last two only if
185    the C++ wrapper was built), and the man pages to appropriate live directories
186    on your system, in the normal way.
187    
188    If you want to remove PCRE from your system, you can run "make uninstall".
189    This removes all the files that "make install" installed. However, it does not
190    remove any directories, because these are often shared with other programs.
191    
192    
193    Retrieving configuration information on Unix-like systems
194    ---------------------------------------------------------
195    
196  Running "make install" also installs the command pcre-config, which can be used  Running "make install" also installs the command pcre-config, which can be used
197  to recall information about the PCRE configuration and installation. For  to recall information about the PCRE configuration and installation. For
198  example,  example:
199    
200    pcre-config --version    pcre-config --version
201    
202  prints the version number, and  prints the version number, and
203    
204   pcre-config --libs    pcre-config --libs
205    
206  outputs information about where the library is installed. This command can be  outputs information about where the library is installed. This command can be
207  included in makefiles for programs that use PCRE, saving the programmer from  included in makefiles for programs that use PCRE, saving the programmer from
208  having to remember too many details.  having to remember too many details.
209    
210  There is one esoteric feature that is controlled by "configure". It concerns  The pkg-config command is another system for saving and retrieving information
211  the character value used for "newline", and is something that you probably do  about installed libraries. Instead of separate commands for each library, a
212  not want to change on a Unix system. The default is to use whatever value your  single command is used. For example:
213  compiler gives to '\n'. By using --enable-newline-is-cr or  
214  --enable-newline-is-lf you can force the value to be CR (13) or LF (10) if you    pkg-config --cflags pcre
215  really want to.  
216    The data is held in *.pc files that are installed in a directory called
217    pkgconfig.
218    
219    
220  Shared libraries on Unix systems  Shared libraries on Unix-like systems
221  --------------------------------  -------------------------------------
222    
223  The default distribution builds PCRE as two shared libraries and two static  The default distribution builds PCRE as shared libraries and static libraries,
224  libraries, as long as the operating system supports shared libraries. Shared  as long as the operating system supports shared libraries. Shared library
225  library support relies on the "libtool" script which is built as part of the  support relies on the "libtool" script which is built as part of the
226  "configure" process.  "configure" process.
227    
228  The libtool script is used to compile and link both shared and static  The libtool script is used to compile and link both shared and static
# Line 115  installed themselves. However, the versi Line 235  installed themselves. However, the versi
235  use the uninstalled libraries.  use the uninstalled libraries.
236    
237  To build PCRE using static libraries only you must use --disable-shared when  To build PCRE using static libraries only you must use --disable-shared when
238  configuring it. For example  configuring it. For example:
239    
240  ./configure --prefix=/usr/gnu --disable-shared  ./configure --prefix=/usr/gnu --disable-shared
241    
# Line 123  Then run "make" in the usual way. Simila Line 243  Then run "make" in the usual way. Simila
243  build only shared libraries.  build only shared libraries.
244    
245    
246    Cross-compiling on a Unix-like system
247    -------------------------------------
248    
249    You can specify CC and CFLAGS in the normal way to the "configure" command, in
250    order to cross-compile PCRE for some other host. However, during the building
251    process, the dftables.c source file is compiled *and run* on the local host, in
252    order to generate the default character tables (the chartables.c file). It
253    therefore needs to be compiled with the local compiler, not the cross compiler.
254    You can do this by specifying CC_FOR_BUILD (and if necessary CFLAGS_FOR_BUILD;
255    there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)
256    when calling the "configure" command. If they are not specified, they default
257    to the values of CC and CFLAGS.
258    
259    
260  Building on non-Unix systems  Building on non-Unix systems
261  ----------------------------  ----------------------------
262    
263  For a non-Unix system, read the comments in the file NON-UNIX-USE. PCRE has  For a non-Unix system, read the comments in the file NON-UNIX-USE, though if
264  been compiled on Windows systems and on Macintoshes, but I don't know the  the system supports the use of "configure" and "make" you may be able to build
265  details because I don't use those systems. It should be straightforward to  PCRE in the same way as for Unix systems.
266    
267    PCRE has been compiled on Windows systems and on Macintoshes, but I don't know
268    the details because I don't use those systems. It should be straightforward to
269  build PCRE on any system that has a Standard C compiler, because it uses only  build PCRE on any system that has a Standard C compiler, because it uses only
270  Standard C functions.  Standard C functions.
271    
# Line 137  Testing PCRE Line 274  Testing PCRE
274  ------------  ------------
275    
276  To test PCRE on a Unix system, run the RunTest script that is created by the  To test PCRE on a Unix system, run the RunTest script that is created by the
277  configuring process. (This can also be run by "make runtest", "make check", or  configuring process. There is also a script called RunGrepTest that tests the
278  "make test".) For other systems, see the instruction in NON-UNIX-USE.  options of the pcregrep command. If the C++ wrapper library is build, three
279    test programs called pcrecpp_unittest, pcre_scanner_unittest, and
280  The script runs the pcretest test program (which is documented in the doc  pcre_stringpiece_unittest are provided.
281  directory) on each of the testinput files (in the testdata directory) in turn,  
282  and compares the output with the contents of the corresponding testoutput file.  Both the scripts and all the program tests are run if you obey "make runtest",
283  A file called testtry is used to hold the output from pcretest. To run pcretest  "make check", or "make test". For other systems, see the instructions in
284  on just one of the test files, give its number as an argument to RunTest, for  NON-UNIX-USE.
285  example:  
286    The RunTest script runs the pcretest test program (which is documented in its
287    RunTest 3  own man page) on each of the testinput files (in the testdata directory) in
288    turn, and compares the output with the contents of the corresponding testoutput
289  The first and third test files can also be fed directly into the perltest  file. A file called testtry is used to hold the main output from pcretest
290  script to check that Perl gives the same results. The third file requires the  (testsavedregex is also used as a working file). To run pcretest on just one of
291  additional features of release 5.005, which is why it is kept separate from the  the test files, give its number as an argument to RunTest, for example:
292  main test input, which needs only Perl 5.004. In the long run, when 5.005 (or  
293  higher) is widespread, these two test files may get amalgamated.    RunTest 2
294    
295    The first file can also be fed directly into the perltest script to check that
296    Perl gives the same results. The only difference you should see is in the first
297    few lines, where the Perl version is given instead of the PCRE version.
298    
299  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),
300  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
# Line 171  listed for checking. Where the compariso Line 312  listed for checking. Where the compariso
312  test will contain [\x00-\xff], and similarly in some other cases. This is not a  test will contain [\x00-\xff], and similarly in some other cases. This is not a
313  bug in PCRE.  bug in PCRE.
314    
315  The fourth set of tests checks pcre_maketables(), the facility for building a  The third set of tests checks pcre_maketables(), the facility for building a
316  set of character tables for a specific locale and using them instead of the  set of character tables for a specific locale and using them instead of the
317  default tables. The tests make use of the "fr" (French) locale. Before running  default tables. The tests make use of the "fr_FR" (French) locale. Before
318  the test, the script checks for the presence of this locale by running the  running the test, the script checks for the presence of this locale by running
319  "locale" command. If that command fails, or if it doesn't include "fr" in the  the "locale" command. If that command fails, or if it doesn't include "fr_FR"
320  list of available locales, the fourth test cannot be run, and a comment is  in the list of available locales, the third test cannot be run, and a comment
321  output to say why. If running this test produces instances of the error  is output to say why. If running this test produces instances of the error
322    
323    ** Failed to set locale "fr"    ** Failed to set locale "fr_FR"
324    
325  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,
326  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.
327    
328  The fifth test checks the experimental, incomplete UTF-8 support. It is not run  The fourth test checks the UTF-8 support. It is not run automatically unless
329  automatically unless PCRE is built with UTF-8 support. This file can be fed  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when
330  directly to the perltest8 script, which requires Perl 5.6 or higher. The sixth  running "configure". This file can be also fed directly to the perltest script,
331  file tests internal UTF-8 features of PCRE that are not relevant to Perl.  provided you are running Perl 5.8 or higher. (For Perl 5.6, a small patch,
332    commented in the script, can be be used.)
333    
334    The fifth test checks error handling with UTF-8 encoding, and internal UTF-8
335    features of PCRE that are not relevant to Perl.
336    
337    The sixth and test checks the support for Unicode character properties. It it
338    not run automatically unless PCRE is built with Unicode property support. To to
339    this you must set --enable-unicode-properties when running "configure".
340    
341    The seventh, eighth, and ninth tests check the pcre_dfa_exec() alternative
342    matching function, in non-UTF-8 mode, UTF-8 mode, and UTF-8 mode with Unicode
343    property support, respectively. The eighth and ninth tests are not run
344    automatically unless PCRE is build with the relevant support.
345    
346    
347  Character tables  Character tables
348  ----------------  ----------------
349    
350  PCRE uses four tables for manipulating and identifying characters. The final  PCRE uses four tables for manipulating and identifying characters whose values
351  argument of the pcre_compile() function is a pointer to a block of memory  are less than 256. The final argument of the pcre_compile() function is a
352  containing the concatenated tables. A call to pcre_maketables() can be used to  pointer to a block of memory containing the concatenated tables. A call to
353  generate a set of tables in the current locale. If the final argument for  pcre_maketables() can be used to generate a set of tables in the current
354  pcre_compile() is passed as NULL, a set of default tables that is built into  locale. If the final argument for pcre_compile() is passed as NULL, a set of
355  the binary is used.  default tables that is built into the binary is used.
356    
357  The source file called chartables.c contains the default set of tables. This is  The source file called chartables.c contains the default set of tables. This is
358  not supplied in the distribution, but is built by the program dftables  not supplied in the distribution, but is built by the program dftables
# Line 238  The distribution should contain the foll Line 392  The distribution should contain the foll
392      headers:      headers:
393    
394    dftables.c            auxiliary program for building chartables.c    dftables.c            auxiliary program for building chartables.c
395    get.c                 )  
   maketables.c          )  
   study.c               ) source of  
   pcre.c                )   the functions  
396    pcreposix.c           )    pcreposix.c           )
397      pcre_compile.c        )
398      pcre_config.c         )
399      pcre_dfa_exec.c       )
400      pcre_exec.c           )
401      pcre_fullinfo.c       )
402      pcre_get.c            ) sources for the functions in the library,
403      pcre_globals.c        )   and some internal functions that they use
404      pcre_info.c           )
405      pcre_maketables.c     )
406      pcre_ord2utf8.c       )
407      pcre_printint.c       )
408      pcre_study.c          )
409      pcre_tables.c         )
410      pcre_try_flipped.c    )
411      pcre_ucp_findchar.c   )
412      pcre_valid_utf8.c     )
413      pcre_version.c        )
414      pcre_xclass.c         )
415    
416      ucp_findchar.c        )
417      ucp.h                 ) source for the code that is used for
418      ucpinternal.h         )   Unicode property handling
419      ucptable.c            )
420      ucptypetable.c        )
421    
422    pcre.in               "source" for the header for the external API; pcre.h    pcre.in               "source" for the header for the external API; pcre.h
423                            is built from this by "configure"                            is built from this by "configure"
424    pcreposix.h           header for the external POSIX wrapper API    pcreposix.h           header for the external POSIX wrapper API
425    internal.h            header for internal use    pcre_internal.h       header for internal use
426    config.in             template for config.h, which is built by configure    config.in             template for config.h, which is built by configure
427    
428      pcrecpp.h.in          "source" for the header file for the C++ wrapper
429      pcrecpp.cc            )
430      pcre_scanner.cc       ) source for the C++ wrapper library
431    
432      pcre_stringpiece.h.in "source" for pcre_stringpiece.h, the header for the
433                              C++ stringpiece functions
434      pcre_stringpiece.cc   source for the C++ stringpiece functions
435    
436  (B) Auxiliary files:  (B) Auxiliary files:
437    
438    AUTHORS               information about the author of PCRE    AUTHORS               information about the author of PCRE
# Line 261  The distribution should contain the foll Line 445  The distribution should contain the foll
445    NON-UNIX-USE          notes on building PCRE on non-Unix systems    NON-UNIX-USE          notes on building PCRE on non-Unix systems
446    README                this file    README                this file
447    RunTest.in            template for a Unix shell script for running tests    RunTest.in            template for a Unix shell script for running tests
448      RunGrepTest.in        template for a Unix shell script for pcregrep tests
449    config.guess          ) files used by libtool,    config.guess          ) files used by libtool,
450    config.sub            )   used only when building a shared library    config.sub            )   used only when building a shared library
451    configure             a configuring shell script (built by autoconf)    configure             a configuring shell script (built by autoconf)
452    configure.in          the autoconf input used to build configure    configure.in          the autoconf input used to build configure
453    doc/Tech.Notes        notes on the encoding    doc/Tech.Notes        notes on the encoding
454    doc/pcre.3            man page source for the PCRE functions    doc/*.3               man page sources for the PCRE functions
455    doc/pcre.html         HTML version    doc/*.1               man page sources for pcregrep and pcretest
456    doc/pcre.txt          plain text version    doc/html/*            HTML documentation
457    doc/pcreposix.3       man page source for the POSIX wrapper API    doc/pcre.txt          plain text version of the man pages
458    doc/pcreposix.html    HTML version    doc/pcretest.txt      plain text documentation of test program
459    doc/pcreposix.txt     plain text version    doc/perltest.txt      plain text documentation of Perl test program
   doc/pcretest.txt      documentation of test program  
   doc/perltest.txt      documentation of Perl test program  
   doc/pcregrep.1        man page source for the pcregrep utility  
   doc/pcregrep.html     HTML version  
   doc/pcregrep.txt      plain text version  
460    install-sh            a shell script for installing files    install-sh            a shell script for installing files
461      libpcre.pc.in         "source" for libpcre.pc for pkg-config
462    ltmain.sh             file used to build a libtool script    ltmain.sh             file used to build a libtool script
463      mkinstalldirs         script for making install directories
464    pcretest.c            comprehensive test program    pcretest.c            comprehensive test program
465    pcredemo.c            simple demonstration of coding calls to PCRE    pcredemo.c            simple demonstration of coding calls to PCRE
466    perltest              Perl test program    perltest              Perl test program
   perltest8             Perl test program for UTF-8 tests  
467    pcregrep.c            source of a grep utility that uses PCRE    pcregrep.c            source of a grep utility that uses PCRE
468    pcre-config.in        source of script which retains PCRE information    pcre-config.in        source of script which retains PCRE information
469    testdata/testinput1   test data, compatible with Perl 5.004 and 5.005    pcrecpp_unittest.c           )
470    testdata/testinput2   test data for error messages and non-Perl things    pcre_scanner_unittest.c      ) test programs for the C++ wrapper
471    testdata/testinput3   test data, compatible with Perl 5.005    pcre_stringpiece_unittest.c  )
472    testdata/testinput4   test data for locale-specific tests    testdata/testinput*   test data for main library tests
473    testdata/testinput5   test data for UTF-8 tests compatible with Perl 5.6    testdata/testoutput*  expected test results
474    testdata/testinput6   test data for other UTF-8 tests    testdata/grep*        input and output for pcregrep tests
   testdata/testoutput1  test results corresponding to testinput1  
   testdata/testoutput2  test results corresponding to testinput2  
   testdata/testoutput3  test results corresponding to testinput3  
   testdata/testoutput4  test results corresponding to testinput4  
   testdata/testoutput5  test results corresponding to testinput5  
   testdata/testoutput6  test results corresponding to testinput6  
475    
476  (C) Auxiliary files for Win32 DLL  (C) Auxiliary files for Win32 DLL
477    
478    dll.mk    libpcre.def
479      libpcreposix.def
480    pcre.def    pcre.def
481    
482  Philip Hazel <ph10@cam.ac.uk>  (D) Auxiliary file for VPASCAL
483  August 2001  
484      makevp.bat
485    
486    Philip Hazel
487    Email local part: ph10
488    Email domain: cam.ac.uk
489    June 2005

Legend:
Removed from v.53  
changed lines
  Added in v.77

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12