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

Diff of /code/trunk/README

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

revision 7 by nigel, Sat Feb 24 21:38:09 2007 UTC revision 53 by nigel, Sat Feb 24 21:39:42 2007 UTC
# Line 1  Line 1 
1  README file for PCRE (Perl-compatible regular expressions)  README file for PCRE (Perl-compatible regular expression library)
2  ----------------------------------------------------------  -----------------------------------------------------------------
3    
4  The distribution should contain the following files:  The latest release of PCRE is always available from
5    
6      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
7    
8    ChangeLog         log of changes to the code  Please read the NEWS file if you are upgrading from a previous release.
   Makefile          for building PCRE  
   Performance       notes on performance  
   README            this file  
   Tech.Notes        notes on the encoding  
   pcre.3            man page for the functions  
   pcreposix.3       man page for the POSIX wrapper API  
   maketables.c      auxiliary program for building chartables.c  
   study.c           ) source of  
   pcre.c            )   the functions  
   pcreposix.c       )  
   pcre.h            header for the external API  
   pcreposix.h       header for the external POSIX wrapper API  
   internal.h        header for internal use  
   pcretest.c        test program  
   pgrep.1           man page for pgrep  
   pgrep.c           source of a grep utility that uses PCRE  
   perltest          Perl test program  
   testinput         test data, compatible with Perl  
   testinput2        test data for error messages and non-Perl things  
   testoutput        test results corresponding to testinput  
   testoutput2       test results corresponding to testinput2  
   
 To build PCRE, edit Makefile for your system (it is a fairly simple make file)  
 and then run it. It builds a two libraries called libpcre.a and libpcreposix.a,  
 a test program called pcretest, and the pgrep command.  
   
 To test PCRE, run pcretest on the file testinput, and compare the output with  
 the contents of testoutput. There should be no differences. For example:  
   
   pcretest testinput some.file  
   diff some.file testoutput  
   
 Do the same with testinput2, comparing the output with testoutput2, but this  
 time using the -i flag for pcretest, i.e.  
   
   pcretest -i testinput2 some.file  
   diff some.file testoutput2  
   
 The make target "runtest" runs both these tests, using the file "testtry" to  
 store the intermediate output, deleting it at the end if all goes well.  
   
 There are two sets of tests because the first set can also be fed directly into  
 the perltest program to check that Perl gives the same results. The second set  
 of tests check pcre_info(), pcre_study(), error detection and run-time flags  
 that are specific to PCRE, as well as the POSIX wrapper API.  
   
 To install PCRE, copy libpcre.a to any suitable library directory (e.g.  
 /usr/local/lib), pcre.h to any suitable include directory (e.g.  
 /usr/local/include), and pcre.3 to any suitable man directory (e.g.  
 /usr/local/man/man3).  
   
 To install the pgrep command, copy it to any suitable binary directory, (e.g.  
 /usr/local/bin) and pgrep.1 to any suitable man directory (e.g.  
 /usr/local/man/man1).  
9    
10  PCRE has its own native API, but a set of "wrapper" functions that are based on  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.a. Note that this  the POSIX API are also supplied in the library libpcreposix. Note that this
12  just provides a POSIX calling interface to PCRE: the regular expressions  just provides a POSIX calling interface to PCRE: the regular expressions
13  themselves still follow Perl syntax and semantics. The header file  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  for the POSIX-style functions is called pcreposix.h. The official POSIX name is
15  regex.h, but I didn't want to risk possible problems with existing files of  regex.h, but I didn't want to risk possible problems with existing files of
16  that name by distributing it that way. To use it with an existing program that  that name by distributing it that way. To use it with an existing program that
17  uses the POSIX API it will have to be renamed or pointed at by a link.  uses the POSIX API, it will have to be renamed or pointed at by a link.
18    
19    
20    Contributions by users of PCRE
21    ------------------------------
22    
23    You can find contributions from PCRE users in the directory
24    
25      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
26    
27    where there is also a README file giving brief descriptions of what they are.
28    Several of them provide support for compiling PCRE on various flavours of
29    Windows systems (I myself do not use Windows). Some are complete in themselves;
30    others are pointers to URLs containing relevant files.
31    
32    
33    Building PCRE on a Unix system
34    ------------------------------
35    
36    To build PCRE on a Unix system, first run the "configure" command from the PCRE
37    distribution directory, with your current directory set to the directory where
38    you want the files to be created. This command is a standard GNU "autoconf"
39    configuration script, for which generic instructions are supplied in INSTALL.
40    
41    Most commonly, people build PCRE within its own distribution directory, and in
42    this case, on many systems, just running "./configure" is sufficient, but the
43    usual methods of changing standard defaults are available. For example,
44    
45    CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
46    
47    specifies that the C compiler should be run with the flags '-O2 -Wall' instead
48    of the default, and that "make install" should install PCRE under /opt/local
49    instead of the default /usr/local.
50    
51    If you want to build in a different directory, just run "configure" with that
52    directory as current. For example, suppose you have unpacked the PCRE source
53    into /source/pcre/pcre-xxx, but you want to build it in /build/pcre/pcre-xxx:
54    
55    cd /build/pcre/pcre-xxx
56    /source/pcre/pcre-xxx/configure
57    
58    If you want to make use of the experimential, incomplete support for UTF-8
59    character strings in PCRE, you must add --enable-utf8 to the "configure"
60    command. Without it, the code for handling UTF-8 is not included in the
61    library. (Even when included, it still has to be enabled by an option at run
62    time.)
63    
64    The "configure" script builds five files:
65    
66    . libtool is a script that builds shared and/or static libraries
67    . Makefile is built by copying Makefile.in and making substitutions.
68    . config.h is built by copying config.in and making substitutions.
69    . pcre-config is built by copying pcre-config.in and making substitutions.
70    . RunTest is a script for running tests
71    
72    Once "configure" has run, you can run "make". It builds two libraries called
73    libpcre and libpcreposix, a test program called pcretest, and the pcregrep
74    command. You can use "make install" to copy these, the public header files
75    pcre.h and pcreposix.h, and the man pages to appropriate live directories on
76    your system, in the normal way.
77    
78    Running "make install" also installs the command pcre-config, which can be used
79    to recall information about the PCRE configuration and installation. For
80    example,
81    
82      pcre-config --version
83    
84    prints the version number, and
85    
86     pcre-config --libs
87    
88    outputs information about where the library is installed. This command can be
89    included in makefiles for programs that use PCRE, saving the programmer from
90    having to remember too many details.
91    
92    There is one esoteric feature that is controlled by "configure". It concerns
93    the character value used for "newline", and is something that you probably do
94    not want to change on a Unix system. The default is to use whatever value your
95    compiler gives to '\n'. By using --enable-newline-is-cr or
96    --enable-newline-is-lf you can force the value to be CR (13) or LF (10) if you
97    really want to.
98    
99    
100    Shared libraries on Unix systems
101    --------------------------------
102    
103    The default distribution builds PCRE as two shared libraries and two static
104    libraries, as long as the operating system supports shared libraries. Shared
105    library support relies on the "libtool" script which is built as part of the
106    "configure" process.
107    
108    The libtool script is used to compile and link both shared and static
109    libraries. They are placed in a subdirectory called .libs when they are newly
110    built. The programs pcretest and pcregrep are built to use these uninstalled
111    libraries (by means of wrapper scripts in the case of shared libraries). When
112    you use "make install" to install shared libraries, pcregrep and pcretest are
113    automatically re-built to use the newly installed shared libraries before being
114    installed themselves. However, the versions left in the source directory still
115    use the uninstalled libraries.
116    
117    To build PCRE using static libraries only you must use --disable-shared when
118    configuring it. For example
119    
120    ./configure --prefix=/usr/gnu --disable-shared
121    
122    Then run "make" in the usual way. Similarly, you can use --disable-static to
123    build only shared libraries.
124    
125    
126    Building on non-Unix systems
127    ----------------------------
128    
129    For a non-Unix system, read the comments in the file NON-UNIX-USE. PCRE has
130    been compiled on Windows systems and on Macintoshes, but I don't know the
131    details because I don't use those systems. It should be straightforward to
132    build PCRE on any system that has a Standard C compiler, because it uses only
133    Standard C functions.
134    
135    
136    Testing PCRE
137    ------------
138    
139    To test PCRE on a Unix system, run the RunTest script that is created by the
140    configuring process. (This can also be run by "make runtest", "make check", or
141    "make test".) For other systems, see the instruction in NON-UNIX-USE.
142    
143    The script runs the pcretest test program (which is documented in the doc
144    directory) on each of the testinput files (in the testdata directory) in turn,
145    and compares the output with the contents of the corresponding testoutput file.
146    A file called testtry is used to hold the output from pcretest. To run pcretest
147    on just one of the test files, give its number as an argument to RunTest, for
148    example:
149    
150      RunTest 3
151    
152    The first and third test files can also be fed directly into the perltest
153    script to check that Perl gives the same results. The third file requires the
154    additional features of release 5.005, which is why it is kept separate from the
155    main test input, which needs only Perl 5.004. In the long run, when 5.005 (or
156    higher) is widespread, these two test files may get amalgamated.
157    
158    The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),
159    pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
160    detection, and run-time flags that are specific to PCRE, as well as the POSIX
161    wrapper API. It also uses the debugging flag to check some of the internals of
162    pcre_compile().
163    
164    If you build PCRE with a locale setting that is not the standard C locale, the
165    character tables may be different (see next paragraph). In some cases, this may
166    cause failures in the second set of tests. For example, in a locale where the
167    isprint() function yields TRUE for characters in the range 128-255, the use of
168    [:isascii:] inside a character class defines a different set of characters, and
169    this shows up in this test as a difference in the compiled code, which is being
170    listed for checking. Where the comparison test output contains [\x00-\x7f] the
171    test will contain [\x00-\xff], and similarly in some other cases. This is not a
172    bug in PCRE.
173    
174    The fourth set of tests checks pcre_maketables(), the facility for building a
175    set of character tables for a specific locale and using them instead of the
176    default tables. The tests make use of the "fr" (French) locale. Before running
177    the test, the script checks for the presence of this locale by running the
178    "locale" command. If that command fails, or if it doesn't include "fr" in the
179    list of available locales, the fourth test cannot be run, and a comment is
180    output to say why. If running this test produces instances of the error
181    
182      ** Failed to set locale "fr"
183    
184    in the comparison output, it means that locale is not available on your system,
185    despite being listed by "locale". This does not mean that PCRE is broken.
186    
187    The fifth test checks the experimental, incomplete UTF-8 support. It is not run
188    automatically unless PCRE is built with UTF-8 support. This file can be fed
189    directly to the perltest8 script, which requires Perl 5.6 or higher. The sixth
190    file tests internal UTF-8 features of PCRE that are not relevant to Perl.
191    
192    
193  Character tables  Character tables
194  ----------------  ----------------
195    
196  PCRE uses four tables for manipulating and identifying characters. These are  PCRE uses four tables for manipulating and identifying characters. The final
197  compiled from a source file called chartables.c. This is not supplied in  argument of the pcre_compile() function is a pointer to a block of memory
198  the distribution, but is built by the program maketables (compiled from  containing the concatenated tables. A call to pcre_maketables() can be used to
199  maketables.c), which uses the ANSI C character handling functions such as  generate a set of tables in the current locale. If the final argument for
200  isalnum(), isalpha(), isupper(), islower(), etc. to build the table sources.  pcre_compile() is passed as NULL, a set of default tables that is built into
201  This means that the default C locale set in your system may affect the contents  the binary is used.
202  of the tables. You can change the tables by editing chartables.c and then  
203  re-building PCRE. If you do this, you should probably also edit Makefile to  The source file called chartables.c contains the default set of tables. This is
204  ensure that the file doesn't ever get re-generated.  not supplied in the distribution, but is built by the program dftables
205    (compiled from dftables.c), which uses the ANSI C character handling functions
206  The first two tables pcre_lcc[] and pcre_fcc[] provide lower casing and a  such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table
207  case flipping functions, respectively. The pcre_cbits[] table consists of four  sources. This means that the default C locale which is set for your system will
208  32-byte bit maps which identify digits, letters, "word" characters, and white  control the contents of these default tables. You can change the default tables
209  space, respectively. These are used when building 32-byte bit maps that  by editing chartables.c and then re-building PCRE. If you do this, you should
210  represent character classes.  probably also edit Makefile to ensure that the file doesn't ever get
211    re-generated.
212    
213    The first two 256-byte tables provide lower casing and case flipping functions,
214    respectively. The next table consists of three 32-byte bit maps which identify
215    digits, "word" characters, and white space, respectively. These are used when
216    building 32-byte bit maps that represent character classes.
217    
218  The pcre_ctypes[] table has bits indicating various character types, as  The final 256-byte table has bits indicating various character types, as
219  follows:  follows:
220    
221      1   white space character      1   white space character
# Line 102  You should not alter the set of characte Line 229  You should not alter the set of characte
229  will cause PCRE to malfunction.  will cause PCRE to malfunction.
230    
231    
232  The pcretest program  Manifest
233  --------------------  --------
234    
235    The distribution should contain the following files:
236    
237    (A) The actual source files of the PCRE library functions and their
238        headers:
239    
240      dftables.c            auxiliary program for building chartables.c
241      get.c                 )
242      maketables.c          )
243      study.c               ) source of
244      pcre.c                )   the functions
245      pcreposix.c           )
246      pcre.in               "source" for the header for the external API; pcre.h
247                              is built from this by "configure"
248      pcreposix.h           header for the external POSIX wrapper API
249      internal.h            header for internal use
250      config.in             template for config.h, which is built by configure
251    
252    (B) Auxiliary files:
253    
254      AUTHORS               information about the author of PCRE
255      ChangeLog             log of changes to the code
256      INSTALL               generic installation instructions
257      LICENCE               conditions for the use of PCRE
258      COPYING               the same, using GNU's standard name
259      Makefile.in           template for Unix Makefile, which is built by configure
260      NEWS                  important changes in this release
261      NON-UNIX-USE          notes on building PCRE on non-Unix systems
262      README                this file
263      RunTest.in            template for a Unix shell script for running tests
264      config.guess          ) files used by libtool,
265      config.sub            )   used only when building a shared library
266      configure             a configuring shell script (built by autoconf)
267      configure.in          the autoconf input used to build configure
268      doc/Tech.Notes        notes on the encoding
269      doc/pcre.3            man page source for the PCRE functions
270      doc/pcre.html         HTML version
271      doc/pcre.txt          plain text version
272      doc/pcreposix.3       man page source for the POSIX wrapper API
273      doc/pcreposix.html    HTML version
274      doc/pcreposix.txt     plain text version
275      doc/pcretest.txt      documentation of test program
276      doc/perltest.txt      documentation of Perl test program
277      doc/pcregrep.1        man page source for the pcregrep utility
278      doc/pcregrep.html     HTML version
279      doc/pcregrep.txt      plain text version
280      install-sh            a shell script for installing files
281      ltmain.sh             file used to build a libtool script
282      pcretest.c            comprehensive test program
283      pcredemo.c            simple demonstration of coding calls to PCRE
284      perltest              Perl test program
285      perltest8             Perl test program for UTF-8 tests
286      pcregrep.c            source of a grep utility that uses PCRE
287      pcre-config.in        source of script which retains PCRE information
288      testdata/testinput1   test data, compatible with Perl 5.004 and 5.005
289      testdata/testinput2   test data for error messages and non-Perl things
290      testdata/testinput3   test data, compatible with Perl 5.005
291      testdata/testinput4   test data for locale-specific tests
292      testdata/testinput5   test data for UTF-8 tests compatible with Perl 5.6
293      testdata/testinput6   test data for other UTF-8 tests
294      testdata/testoutput1  test results corresponding to testinput1
295      testdata/testoutput2  test results corresponding to testinput2
296      testdata/testoutput3  test results corresponding to testinput3
297      testdata/testoutput4  test results corresponding to testinput4
298      testdata/testoutput5  test results corresponding to testinput5
299      testdata/testoutput6  test results corresponding to testinput6
300    
301  This program is intended for testing PCRE, but it can also be used for  (C) Auxiliary files for Win32 DLL
 experimenting with regular expressions.  
302    
303  If it is given two filename arguments, it reads from the first and writes to    dll.mk
304  the second. If it is given only one filename argument, it reads from that file    pcre.def
 and writes to stdout. Otherwise, it reads from stdin and writes to stdout, and  
 prompts for each line of input.  
   
 The program handles any number of sets of input on a single input file. Each  
 set starts with a regular expression, and continues with any number of data  
 lines to be matched against the pattern. An empty line signals the end of the  
 set. The regular expressions are given enclosed in any non-alphameric  
 delimiters, for example  
   
   /(a|bc)x+yz/  
   
 and may be followed by i, m, s, or x to set the PCRE_CASELESS, PCRE_MULTILINE,  
 PCRE_DOTALL, or PCRE_EXTENDED options, respectively. These options have the  
 same effect as they do in Perl.  
   
 There are also some upper case options that do not match Perl options: /A, /E,  
 and /X set PCRE_ANCHORED, PCRE_DOLLAR_ENDONLY, and PCRE_EXTRA respectively.  
 The /D option is a PCRE debugging feature. It causes the internal form of  
 compiled regular expressions to be output after compilation. The /S option  
 causes pcre_study() to be called after the expression has been compiled, and  
 the results used when the expression is matched. If /I is present as well as  
 /S, then pcre_study() is called with the PCRE_CASELESS option.  
   
 Finally, the /P option causes pcretest to call PCRE via the POSIX wrapper API  
 rather than its native API. When this is done, all other options except /i and  
 /m are ignored. REG_ICASE is set if /i is present, and REG_NEWLINE is set if /m  
 is present. The wrapper functions force PCRE_DOLLAR_ENDONLY always, and  
 PCRE_DOTALL unless REG_NEWLINE is set.  
   
 A regular expression can extend over several lines of input; the newlines are  
 included in it. See the testinput file for many examples.  
   
 Before each data line is passed to pcre_exec(), leading and trailing whitespace  
 is removed, and it is then scanned for \ escapes. The following are recognized:  
   
   \a     alarm (= BEL)  
   \b     backspace  
   \e     escape  
   \f     formfeed  
   \n     newline  
   \r     carriage return  
   \t     tab  
   \v     vertical tab  
   \nnn   octal character (up to 3 octal digits)  
   \xhh   hexadecimal character (up to 2 hex digits)  
   
   \A     pass the PCRE_ANCHORED option to pcre_exec()  
   \B     pass the PCRE_NOTBOL option to pcre_exec()  
   \E     pass the PCRE_DOLLAR_ENDONLY option to pcre_exec()  
   \I     pass the PCRE_CASELESS option to pcre_exec()  
   \M     pass the PCRE_MULTILINE option to pcre_exec()  
   \S     pass the PCRE_DOTALL option to pcre_exec()  
   \Odd   set the size of the output vector passed to pcre_exec() to dd  
            (any number of decimal digits)  
   \Z     pass the PCRE_NOTEOL option to pcre_exec()  
   
 A backslash followed by anything else just escapes the anything else. If the  
 very last character is a backslash, it is ignored. This gives a way of passing  
 an empty line as data, since a real empty line terminates the data input.  
   
 If /P was present on the regex, causing the POSIX wrapper API to be used, only  
 \B, and \Z have any effect, causing REG_NOTBOL and REG_NOTEOL to be passed to  
 regexec() respectively.  
   
 When a match succeeds, pcretest outputs the list of identified substrings that  
 pcre_exec() returns, starting with number 0 for the string that matched the  
 whole pattern. Here is an example of an interactive pcretest run.  
   
   $ pcretest  
   Testing Perl-Compatible Regular Expressions  
   PCRE version 0.90 08-Sep-1997  
   
       re> /^abc(\d+)/  
     data> abc123  
    0: abc123  
    1: 123  
     data> xyz  
   No match  
   
 Note that while patterns can be continued over several lines (a plain ">"  
 prompt is used for continuations), data lines may not. However newlines can be  
 included in data by means of the \n escape.  
   
 If the -p option is given to pcretest, it is equivalent to adding /P to each  
 regular expression: the POSIX wrapper API is used to call PCRE. None of the  
 following flags has any effect in this case.  
   
 If the option -d is given to pcretest, it is equivalent to adding /D to each  
 regular expression: the internal form is output after compilation.  
   
 If the option -i (for "information") is given to pcretest, it calls pcre_info()  
 after compiling an expression, and outputs the information it gets back. If the  
 pattern is studied, the results of that are also output.  
   
 If the option -s is given to pcretest, it outputs the size of each compiled  
 pattern after it has been compiled.  
   
 If the -t option is given, each compile, study, and match is run 2000 times  
 while being timed, and the resulting time per compile or match is output in  
 milliseconds. Do not set -t with -s, because you will then get the size output  
 2000 times and the timing will be distorted.  
   
   
   
 The perltest program  
 --------------------  
   
 The perltest program tests Perl's regular expressions; it has the same  
 specification as pcretest, and so can be given identical input, except that  
 input patterns can be followed only by Perl's lower case options.  
   
 The data lines are processed as Perl strings, so if they contain $ or @  
 characters, these have to be escaped. For this reason, all such characters in  
 the testinput file are escaped so that it can be used for perltest as well as  
 for pcretest, and the special upper case options such as /A that pcretest  
 recognizes are not used in this file. The output should be identical, apart  
 from the initial identifying banner.  
   
 The testinput2 file is not suitable for feeding to Perltest, since it does  
 make use of the special upper case options and escapes that pcretest uses to  
 test additional features of PCRE.  
305    
306  Philip Hazel <ph10@cam.ac.uk>  Philip Hazel <ph10@cam.ac.uk>
307  October 1997  August 2001
Legend:
Removed from v.7  
changed lines
  Added in v.53
  ViewVC Help
Powered by ViewVC 1.1.5