9c8abddc52
* pcre2test: use the right header for libedit in FreeBSD with autoconf When `./configure --enable-pcre2test-libedit` is used in FreeBSD, the resulting test will succeed but won't set the necessary flag to distinguish between libedit and readline header files, therefore using readline's at built time (if installed) Consolidate all header tests into one and use instead the corresponding autogenerated defines to check for each possibility. * pcre2test: really allow libedit with cmake Using cmake to configure and enable linking pcre2test with libedit, could result in a broken build, because the header used was instead pointing to readline. In cases were the build will succeed (because both libraries were available), it would likely show warnings, because several history functions were being used without declarations, since readline requires including "history.h" for those. Additionally, since PCRE2_SUPPORT_READLINE is ON by default (unlike configure), turning PCRE2_SUPPORT_LIBEDIT=ON, would require setting that other option to OFF explicitly (even if readline wasn't available) or the setup would abort. Lastly, in systems with no default sysroot (ex: macOS), the use of absolute paths for searching for libedit's readline.h could fail so use instead relative PATH_SUFFIXES. * pcre2test: avoid using readline headers with libedit When asked to enable libedit in a system that ALSO has readline, the headers of the former would be found and used by the earlier. While that would mostly work, some functions will be missing definitions (which is forbidden in C99), so instead abort the configuration and let the user provide for them. |
||
|---|---|---|
| cmake | ||
| doc | ||
| m4 | ||
| maint | ||
| src | ||
| testdata | ||
| .gitignore | ||
| 132html | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| COPYING | ||
| ChangeLog | ||
| CheckMan | ||
| CleanTxt | ||
| Detrail | ||
| HACKING | ||
| LICENCE | ||
| Makefile.am | ||
| NEWS | ||
| NON-AUTOTOOLS-BUILD | ||
| PrepareRelease | ||
| README | ||
| README.md | ||
| RunGrepTest | ||
| RunGrepTest.bat | ||
| RunTest | ||
| RunTest.bat | ||
| autogen.sh | ||
| config-cmake.h.in | ||
| configure.ac | ||
| index.md | ||
| libpcre2-8.pc.in | ||
| libpcre2-16.pc.in | ||
| libpcre2-32.pc.in | ||
| libpcre2-posix.pc.in | ||
| pcre2-config.in | ||
| pcre2_fuzzer.dict | ||
| pcre2_fuzzer.options | ||
| perltest.sh | ||
README.md
PCRE2 - Perl-Compatible Regular Expressions
The PCRE2 library is a set of C functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE2 has its own native API, as well as a set of wrapper functions that correspond to the POSIX regular expression API. The PCRE2 library is free, even for building proprietary software. It comes in three forms, for processing 8-bit, 16-bit, or 32-bit code units, in either literal or UTF encoding.
PCRE2 was first released in 2015 to replace the API in the original PCRE library, which is now obsolete and no longer maintained. As well as a more flexible API, the code of PCRE2 has been much improved since the fork.
Download
As well as downloading from the GitHub site, you can download PCRE2 or the older, unmaintained PCRE1 library from an unofficial mirror at SourceForge.
You can check out the PCRE2 source code via Git or Subversion:
git clone https://github.com/PhilipHazel/pcre2.git
svn co https://github.com/PhilipHazel/pcre2.git
Contributed Ports
If you just need the command-line PCRE2 tools on Windows, precompiled binary versions are available at this Rexegg page.
A PCRE2 port for z/OS, a mainframe operating system which uses EBCDIC as its default character encoding, can be found at http://www.cbttape.org (File 939).
Documentation
You can read the PCRE2 documentation here.
Comparisons to Perl's regular expression semantics can be found in the community authored Wikipedia entry for PCRE.
There is a curated summary of changes for each PCRE release, copies of documentation from older releases, and other useful information from the third party authored RexEgg PCRE Documentation and Change Log page.
Contact
To report a problem with the PCRE2 library, or to make a feature request, please use the PCRE2 GitHub issues tracker. There is a mailing list for discussion of PCRE2 issues and development at pcre2-dev@googlegroups.com, which is where any announcements will be made. You can browse the list archives.