Pcre-8.31.tar.bz2 download.PCRE - Perl Compatible Regular Expressions

Looking for:

Pcre-8.31.tar.bz2 download 

Click here to DOWNLOAD

     

Pcre-8.31.tar.bz2 download.Download File List - PCRE - OSDN

 

The default newline indicator is a single LF character the Unix standard. You can specify the default newline indicator by adding --enable-newline-is-cr or --enable-newline-is-lf or --enable-newline-is-crlf or --enable-newline-is-anycrlf or --enable-newline-is-any to the "configure" command, respectively.

If you specify --enable-newline-is-cr or --enable-newline-is-crlf, some of the standard tests will fail, because the lines in the test files end with LF.

Even if the files are edited to change the line endings, there are likely to be some failures. With --enable-newline-is-anycrlf or --enable-newline-is-any, many tests should succeed, but there may be some failures. This is independent of the option specifying what PCRE considers to be the end of a line see above.

PCRE has a counter that limits the depth of nesting of parentheses in a pattern. This limits the amount of system stack that a pattern uses when it is compiled. PCRE has a counter that can be set to limit the amount of resources it uses when matching a pattern.

If the limit is exceeded during a match, the match fails. The default is ten million. There is more discussion on the pcreapi man page. There is a separate counter that limits the depth of recursive function calls during a matching process. This also has a default of ten million, which is essentially "unlimited". There is a discussion about stack sizes in the pcrestack man page. The default maximum compiled pattern size is around 64K.

In the 8-bit library, PCRE then uses three bytes instead of two for offsets to different parts of the compiled pattern.

Increasing the internal link size reduces performance. In the bit library, the only supported link size is 4. 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.

For speed, PCRE uses four tables for manipulating and identifying characters whose code point values are less than If you specify --enable-rebuild-chartables a program called dftables is compiled and run in the default C locale when you obey "make". See "Character tables" below for further information.

In environments where valgrind is installed, if you specify --enable-valgrind PCRE will use valgrind annotations to mark certain memory regions as unaddressable. This allows it to detect invalid memory accesses, and is mostly useful for debugging PCRE itself. In environments where the gcc compiler is used and lcov version 1. The report is generated by running "make coverage". If ccache is installed on your system, it must be disabled when building PCRE for coverage reporting.

There is more information about coverage reporting in the "pcrebuild" documentation. The pcregrep program currently supports only 8-bit data files, and so requires the 8-bit PCRE library. The default is It is possible to compile pcretest so that it links with the libreadline or libedit libraries, by specifying, respectively, --enable-pcretest-libreadline or --enable-pcretest-libedit If this is done, when pcretest's input is from a terminal, it reads it using the readline function.

This provides line-editing and history facilities. Note that libreadline is GPL-licenced, so if you distribute a binary of pcretest linked in this way, there may be licensing issues. These can be avoided by linking with libedit which has a BSD licence instead. Enabling libreadline causes the -lreadline option to be added to the pcretest build.

In many operating environments with a sytem-installed readline library this is sufficient. However, in some environments e. This is because, to quote the readline INSTALL, "Readline uses the termcap functions, but does not link with the termcap or curses library itself, allowing applications which link with readline the to choose an appropriate library. The "configure" script builds the following files for the basic C library:. Makefile the makefile that builds the library. If you use "configure" or CMake, the.

Once "configure" has run, you can run "make". The command "make check" runs all the appropriate tests. Details of the PCRE tests are given below in a separate section of this document. You can use "make install" to install PCRE into live directories on your system. This removes all the files that "make install" installed. However, it does not remove any directories, because these are often shared with other programs. Retrieving configuration information Running "make install" installs the command pcre-config, which can be used to recall information about the PCRE configuration and installation.

For example: pcre-config --version prints the version number, and pcre-config --libs outputs information about where the library is installed. This command can be included in makefiles for programs that use PCRE, saving the programmer from having to remember too many details. The pkg-config command is another system for saving and retrieving information about installed libraries.

Instead of separate commands for each library, a single command is used. Shared libraries The default distribution builds PCRE as shared libraries and static libraries, as long as the operating system supports shared libraries. Shared library support relies on the "libtool" script which is built as part of the "configure" process. The libtool script is used to compile and link both shared and static libraries.

They are placed in a subdirectory called. The programs pcretest and pcregrep are built to use these uninstalled libraries by means of wrapper scripts in the case of shared libraries. When you use "make install" to install shared libraries, pcregrep and pcretest are automatically re-built to use the newly installed shared libraries before being installed themselves.

However, the versions left in the build directory still use the uninstalled libraries. To build PCRE using static libraries only you must use --disable-shared when configuring it. For example:. Similarly, you can use --disable-static to build only shared libraries.

However, you should NOT specify --enable-rebuild-chartables, because if you do, the dftables. This will probably not work, because dftables. Cross-compiling with the default tables should not be a problem. Then when you cross-compile PCRE this new version of the tables will be used.

Using Sun's compilers for Solaris A user reports that the following configurations work on Solaris 9 sparcv9 and Solaris 9 x86 bit : Solaris 9 sparcv The command "make distcheck" does the same, but then does a trial build of the new distribution to ensure that it works. If you have modified any of the man page sources in the doc directory, you should first run the PrepareRelease script before making a distribution. This script creates the. There is another script called RunGrepTest that tests the options of the pcregrep command.

Both the scripts and all the program tests are run if you obey "make check" or "make test". The RunTest script runs the pcretest test program which is documented in its own man page on each of the relevant testinput files in the testdata directory, and compares the output with the contents of the corresponding testoutput files.

RunTest uses a file called testtry to hold the main output from pcretest. Other files whose names begin with "test" are used as working files in some tests. Some tests are relevant only when certain build-time options were selected. RunTest outputs a comment when it skips a test. Many of the tests that are not skipped are run up to three times. This testing can be suppressed by putting "nojit" on the RunTest command line.

The entire set of tests is run once for each of the 8-bit, bit and bit libraries that are enabled. If you want to run just one set of tests, call RunTest with either the -8, or option. If valgrind is installed, you can run the tests under it by putting "valgrind" on the RunTest command line. Whatever order the arguments are in, the tests are always run in numerical order. You can also call RunTest with the single argument "list" to cause it to output a list of tests. The first test file can be fed directly into the perltest.

The only difference you should see is in the first few lines, where the Perl version is given instead of the PCRE version. If you build PCRE with a locale setting that is not the standard C locale, the character tables may be different see next paragraph. In some cases, this may cause failures in the second set of tests.

For example, in a locale where the isprint function yields TRUE for characters in the range , the use of [:isascii:] inside a character class defines a different set of characters, and this shows up in this test as a difference in the compiled code, which is being listed for checking. This is not a bug in PCRE. Before running the test, the script checks for the presence of this locale by running the "locale" command.

This does not mean that PCRE is broken. Alternatively, use RunTest. The version of RunTest. This version of PCRE is now at end of life, and is no longer being actively maintained. Version 8. Note that the former ftp. For Perl 5 regular expression syntax, read the Perl regular expressions man page. Note that bugs in the legacy PCRE release are unlikely to be looked at or fixed; and please don't use the SourceForge bug tracking system, as it is not normally monitored.

There is a mailing list for active PCRE developers at pcre2-dev googlegroups.