/[pcre]/code/branches/pcre16/README

Diff of /code/branches/pcre16/README

Parent Directory | Revision Log | View Patch Patch

-revision 65 by nigel,
Sat Feb 24 21:40:08 2007 UTC
+revision 73 by nigel,
Sat Feb 24 21:40:30 2007 UTC
 Line 16 
 regex.h, but I didn't want to risk possi
  that name by distributing it that way. To use it with an existing program that
  uses the POSIX API, it will have to be renamed or pointed at by a link.
+ If you are using the POSIX interface to PCRE and there is already a POSIX regex
+ library installed on your system, you must take care when linking programs to
+ ensure that they link with PCRE's libpcreposix library. Otherwise they may pick
+ up the "real" POSIX functions of the same name.
  Contributions by users of PCRE
  ------------------------------
-Line 96 
 library. You can read more about them in
+Line 101 
 library. You can read more about them in
    is a representation of the compiled pattern, and this changes with the link
    size.
+ . You can build PCRE so that its match() function does not call itself
+   recursively. Instead, it uses blocks of data from the heap via special
+   functions pcre_stack_malloc() and pcre_stack_free() to save data that would
+   otherwise be saved on the stack. To build PCRE like this, use
+   --disable-stack-for-recursion
+   on the "configure" command. PCRE runs more slowly in this mode, but it may be
+   necessary in environments with limited stack sizes.
  The "configure" script builds five files:
  . libtool is a script that builds shared and/or static libraries
-Line 125 
 included in makefiles for programs that
+Line 140 
 included in makefiles for programs that
  having to remember too many details.
- Cross-compiling PCRE on a Unix-like system
- ------------------------------------------
- PCRE needs to compile and run an auxiliary program as part of the building
- process. Obviously, if the real compilation is for some other system, it can't
- use the same CC and CFLAGS values when it is doing this. For cross compilation,
- therefore, you must set CC_FOR_BUILD to the local host's compiler, and you can
- set flags in CFLAGS_FOR_BUILD if you need to.
  Shared libraries on Unix-like systems
  -------------------------------------
-Line 169 
 order to cross-compile PCRE for some oth
+Line 174 
 order to cross-compile PCRE for some oth
  process, the dftables.c source file is compiled *and run* on the local host, in
  order to generate the default character tables (the chartables.c file). It
  therefore needs to be compiled with the local compiler, not the cross compiler.
- You can do this by specifying HOST_CC (and if necessary HOST_CFLAGS) when
+ You can do this by specifying CC_FOR_BUILD (and if necessary CFLAGS_FOR_BUILD)
- calling the "configure" command. If they are not specified, they default to the
+ when calling the "configure" command. If they are not specified, they default
- values of CC and CFLAGS.
+ to the values of CC and CFLAGS.
  Building on non-Unix systems
  ----------------------------
- 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
- 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
- details because I don't use those systems. It should be straightforward to
+ PCRE in the same way as for Unix systems.
+ PCRE has been compiled on Windows systems and on Macintoshes, but I don't know
+ the details because I don't use those systems. It should be straightforward to
  build PCRE on any system that has a Standard C compiler, because it uses only
  Standard C functions.
-Line 189 
 Testing PCRE
+Line 197 
 Testing PCRE
  To test PCRE on a Unix system, run the RunTest script that is created by the
  configuring process. (This can also be run by "make runtest", "make check", or
- "make test".) For other systems, see the instruction in NON-UNIX-USE.
+ "make test".) For other systems, see the instructions in NON-UNIX-USE.
  The script runs the pcretest test program (which is documented in its own man
  page) on each of the testinput files (in the testdata directory) in turn,
-Line 222 
 bug in PCRE.
+Line 230 
 bug in PCRE.
  The third set of tests checks pcre_maketables(), the facility for building a
  set of character tables for a specific locale and using them instead of the
- 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
- 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
- "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"
- list of available locales, the third test cannot be run, and a comment is
+ in the list of available locales, the third test cannot be run, and a comment
- 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
-   ** Failed to set locale "fr"
+   ** Failed to set locale "fr_FR"
  in the comparison output, it means that locale is not available on your system,
  despite being listed by "locale". This does not mean that PCRE is broken.
-Line 354 
 The distribution should contain the foll
+Line 362 
 The distribution should contain the foll
    makevp.bat
  Philip Hazel <ph10@cam.ac.uk>
- February 2003
+ December 2003

 Legend:



Removed from v.65
 


changed lines


 
Added in v.73
 Legend:



Removed from v.65
 


changed lines


 
Added in v.73
-Removed from v.65
+Added in v.73

	ViewVC Help
Powered by ViewVC 1.1.5