head 1.10; access; symbols pkgsrc-2026Q1:1.10.0.38 pkgsrc-2026Q1-base:1.10 pkgsrc-2025Q4:1.10.0.36 pkgsrc-2025Q4-base:1.10 pkgsrc-2025Q3:1.10.0.34 pkgsrc-2025Q3-base:1.10 pkgsrc-2025Q2:1.10.0.32 pkgsrc-2025Q2-base:1.10 pkgsrc-2025Q1:1.10.0.30 pkgsrc-2025Q1-base:1.10 pkgsrc-2024Q4:1.10.0.28 pkgsrc-2024Q4-base:1.10 pkgsrc-2024Q3:1.10.0.26 pkgsrc-2024Q3-base:1.10 pkgsrc-2024Q2:1.10.0.24 pkgsrc-2024Q2-base:1.10 pkgsrc-2024Q1:1.10.0.22 pkgsrc-2024Q1-base:1.10 pkgsrc-2023Q4:1.10.0.20 pkgsrc-2023Q4-base:1.10 pkgsrc-2023Q3:1.10.0.18 pkgsrc-2023Q3-base:1.10 pkgsrc-2023Q2:1.10.0.16 pkgsrc-2023Q2-base:1.10 pkgsrc-2023Q1:1.10.0.14 pkgsrc-2023Q1-base:1.10 pkgsrc-2022Q4:1.10.0.12 pkgsrc-2022Q4-base:1.10 pkgsrc-2022Q3:1.10.0.10 pkgsrc-2022Q3-base:1.10 pkgsrc-2022Q2:1.10.0.8 pkgsrc-2022Q2-base:1.10 pkgsrc-2022Q1:1.10.0.6 pkgsrc-2022Q1-base:1.10 pkgsrc-2021Q4:1.10.0.4 pkgsrc-2021Q4-base:1.10 pkgsrc-2021Q3:1.10.0.2 pkgsrc-2021Q3-base:1.10 pkgsrc-2021Q2:1.9.0.54 pkgsrc-2021Q2-base:1.9 pkgsrc-2021Q1:1.9.0.52 pkgsrc-2021Q1-base:1.9 pkgsrc-2020Q4:1.9.0.50 pkgsrc-2020Q4-base:1.9 pkgsrc-2020Q3:1.9.0.48 pkgsrc-2020Q3-base:1.9 pkgsrc-2020Q2:1.9.0.44 pkgsrc-2020Q2-base:1.9 pkgsrc-2020Q1:1.9.0.24 pkgsrc-2020Q1-base:1.9 pkgsrc-2019Q4:1.9.0.46 pkgsrc-2019Q4-base:1.9 pkgsrc-2019Q3:1.9.0.42 pkgsrc-2019Q3-base:1.9 pkgsrc-2019Q2:1.9.0.40 pkgsrc-2019Q2-base:1.9 pkgsrc-2019Q1:1.9.0.38 pkgsrc-2019Q1-base:1.9 pkgsrc-2018Q4:1.9.0.36 pkgsrc-2018Q4-base:1.9 pkgsrc-2018Q3:1.9.0.34 pkgsrc-2018Q3-base:1.9 pkgsrc-2018Q2:1.9.0.32 pkgsrc-2018Q2-base:1.9 pkgsrc-2018Q1:1.9.0.30 pkgsrc-2018Q1-base:1.9 pkgsrc-2017Q4:1.9.0.28 pkgsrc-2017Q4-base:1.9 pkgsrc-2017Q3:1.9.0.26 pkgsrc-2017Q3-base:1.9 pkgsrc-2017Q2:1.9.0.22 pkgsrc-2017Q2-base:1.9 pkgsrc-2017Q1:1.9.0.20 pkgsrc-2017Q1-base:1.9 pkgsrc-2016Q4:1.9.0.18 pkgsrc-2016Q4-base:1.9 pkgsrc-2016Q3:1.9.0.16 pkgsrc-2016Q3-base:1.9 pkgsrc-2016Q2:1.9.0.14 pkgsrc-2016Q2-base:1.9 pkgsrc-2016Q1:1.9.0.12 pkgsrc-2016Q1-base:1.9 pkgsrc-2015Q4:1.9.0.10 pkgsrc-2015Q4-base:1.9 pkgsrc-2015Q3:1.9.0.8 pkgsrc-2015Q3-base:1.9 pkgsrc-2015Q2:1.9.0.6 pkgsrc-2015Q2-base:1.9 pkgsrc-2015Q1:1.9.0.4 pkgsrc-2015Q1-base:1.9 pkgsrc-2014Q4:1.9.0.2 pkgsrc-2014Q4-base:1.9 pkgsrc-2014Q3:1.8.0.22 pkgsrc-2014Q3-base:1.8 pkgsrc-2014Q2:1.8.0.20 pkgsrc-2014Q2-base:1.8 pkgsrc-2014Q1:1.8.0.18 pkgsrc-2014Q1-base:1.8 pkgsrc-2013Q4:1.8.0.16 pkgsrc-2013Q4-base:1.8 pkgsrc-2013Q3:1.8.0.14 pkgsrc-2013Q3-base:1.8 pkgsrc-2013Q2:1.8.0.12 pkgsrc-2013Q2-base:1.8 pkgsrc-2013Q1:1.8.0.10 pkgsrc-2013Q1-base:1.8 pkgsrc-2012Q4:1.8.0.8 pkgsrc-2012Q4-base:1.8 pkgsrc-2012Q3:1.8.0.6 pkgsrc-2012Q3-base:1.8 pkgsrc-2012Q2:1.8.0.4 pkgsrc-2012Q2-base:1.8 pkgsrc-2012Q1:1.8.0.2 pkgsrc-2012Q1-base:1.8 pkgsrc-2011Q4:1.6.0.4 pkgsrc-2011Q4-base:1.6 pkgsrc-2011Q3:1.6.0.2 pkgsrc-2011Q3-base:1.6 pkgsrc-2011Q2:1.5.0.30 pkgsrc-2011Q2-base:1.5 pkgsrc-2011Q1:1.5.0.28 pkgsrc-2011Q1-base:1.5 pkgsrc-2010Q4:1.5.0.26 pkgsrc-2010Q4-base:1.5 pkgsrc-2010Q3:1.5.0.24 pkgsrc-2010Q3-base:1.5 pkgsrc-2010Q2:1.5.0.22 pkgsrc-2010Q2-base:1.5 pkgsrc-2010Q1:1.5.0.20 pkgsrc-2010Q1-base:1.5 pkgsrc-2009Q4:1.5.0.18 pkgsrc-2009Q4-base:1.5 pkgsrc-2009Q3:1.5.0.16 pkgsrc-2009Q3-base:1.5 pkgsrc-2009Q2:1.5.0.14 pkgsrc-2009Q2-base:1.5 pkgsrc-2009Q1:1.5.0.12 pkgsrc-2009Q1-base:1.5 pkgsrc-2008Q4:1.5.0.10 pkgsrc-2008Q4-base:1.5 pkgsrc-2008Q3:1.5.0.8 pkgsrc-2008Q3-base:1.5 cube-native-xorg:1.5.0.6 cube-native-xorg-base:1.5 pkgsrc-2008Q2:1.5.0.4 pkgsrc-2008Q2-base:1.5 cwrapper:1.5.0.2 pkgsrc-2008Q1:1.4.0.8 pkgsrc-2008Q1-base:1.4 pkgsrc-2007Q4:1.4.0.6 pkgsrc-2007Q4-base:1.4 pkgsrc-2007Q3:1.4.0.4 pkgsrc-2007Q3-base:1.4 pkgsrc-2007Q2:1.4.0.2 pkgsrc-2007Q2-base:1.4 pkgsrc-2007Q1:1.3.0.10 pkgsrc-2007Q1-base:1.3 pkgsrc-2006Q4:1.3.0.8 pkgsrc-2006Q4-base:1.3 pkgsrc-2006Q3:1.3.0.6 pkgsrc-2006Q3-base:1.3 pkgsrc-2006Q2:1.3.0.4 pkgsrc-2006Q2-base:1.3 pkgsrc-2006Q1:1.3.0.2 pkgsrc-2006Q1-base:1.3 pkgsrc-2005Q4:1.2.0.10 pkgsrc-2005Q4-base:1.2 pkgsrc-2005Q3:1.2.0.8 pkgsrc-2005Q3-base:1.2 pkgsrc-2005Q2:1.2.0.6 pkgsrc-2005Q2-base:1.2 pkgsrc-2005Q1:1.2.0.4 pkgsrc-2005Q1-base:1.2 pkgsrc-2004Q4:1.2.0.2 pkgsrc-2004Q4-base:1.2 pkgsrc-2004Q3:1.1.0.10 pkgsrc-2004Q3-base:1.1 pkgsrc-2004Q2:1.1.0.8 pkgsrc-2004Q2-base:1.1 pkgsrc-2004Q1:1.1.0.6 pkgsrc-2004Q1-base:1.1 pkgsrc-2003Q4:1.1.0.4 pkgsrc-2003Q4-base:1.1 netbsd-1-6-1:1.1.0.2 netbsd-1-6-1-base:1.1; locks; strict; comment @# @; 1.10 date 2021.06.24.14.41.23; author adam; state Exp; branches; next 1.9; commitid PYx4HB1tzEOLvoYC; 1.9 date 2014.11.30.14.48.43; author spz; state Exp; branches; next 1.8; commitid vuJGaNnsRaCcDd0y; 1.8 date 2012.03.10.08.03.57; author sbd; state Exp; branches 1.8.22.1; next 1.7; 1.7 date 2012.03.02.15.24.48; author wiz; state Exp; branches; next 1.6; 1.6 date 2011.08.22.12.58.08; author wiz; state Exp; branches; next 1.5; 1.5 date 2008.05.27.16.20.52; author tnn; state Exp; branches; next 1.4; 1.4 date 2007.05.03.12.27.55; author wiz; state dead; branches; next 1.3; 1.3 date 2006.02.04.17.13.49; author wiz; state Exp; branches; next 1.2; 1.2 date 2004.09.28.15.59.49; author wiz; state Exp; branches; next 1.1; 1.1 date 2002.12.30.18.08.02; author cjep; state Exp; branches; next ; 1.8.22.1 date 2014.12.04.19.28.20; author tron; state Exp; branches; next ; commitid Vy27BgR80t4j3L0y; desc @@ 1.10 log @pcre: updated to 8.45 Release 8.45 15-June-2021 ----------------------------- This is the final PCRE1 release. A very few small issues have been fixed. @ text @$NetBSD: patch-ab,v 1.9 2014/11/30 14:48:43 spz Exp $ Remove a feeble attempt at providing ABI compatibility for the C++ portion of the PCRE library. Relying on the C++ compiler to crunch symbols in a particular way is platform dependent at best, and the comments indicate that this was done for OSX. Also, the test misfired on SunOS leading to breakage (PR pkg/38768). --- configure.orig 2021-06-15 15:52:52.000000000 +0000 +++ configure @@@@ -19291,6 +19291,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS ac_link='$CXX -o conftest$ac_exeext $CXXFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' ac_compiler_gnu=$ac_cv_cxx_compiler_gnu +# XXX pkgsrc +if false; then # Older versions of pcre defined pcrecpp::no_arg, but in new versions # it's called pcrecpp::RE::no_arg. For backwards ABI compatibility, @@@@ -19334,6 +19336,9 @@@@ rm -f core conftest.err conftest.$ac_obj done LDFLAGS="$OLD_LDFLAGS" +# XXX pkgsrc +fi + # We could be more clever here, given we're doing AC_SUBST with this # (eg set a var to be the name of the include file we want). But we're not # so it's easy to change back to 'regular' autoconf vars if we needed to. @@@@ -20637,6 +20642,10 @@@@ elif test "$enable_pcretest_libreadline" printf "%s\n" "#define SUPPORT_LIBREADLINE /**/" >>confdefs.h +else + +LIBREADLINE= + fi @ 1.9 log @patch for CVE-2014-8964 from upstream also, patch refresh @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.8 2012/03/10 08:03:57 sbd Exp $ d9 1 a9 1 --- configure.orig 2014-09-26 09:06:46.000000000 +0000 d11 1 a11 1 @@@@ -17603,6 +17603,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS d20 1 a20 1 @@@@ -17645,6 +17647,9 @@@@ rm -f core conftest.err conftest.$ac_obj d30 1 a30 1 @@@@ -18952,6 +18957,10 @@@@ elif test "$enable_pcretest_libreadline" d32 1 a32 1 $as_echo "#define SUPPORT_LIBREADLINE /**/" >>confdefs.h @ 1.8 log @If libreadline isn't wanted don't put it in a programs LDADD variable. Bump PKGREVISION @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.7 2012/03/02 15:24:48 wiz Exp $ d9 1 a9 1 --- configure.orig 2012-02-04 12:55:43.000000000 +0000 d11 1 a11 1 @@@@ -16189,6 +16189,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS d20 1 a20 1 @@@@ -16231,6 +16233,9 @@@@ rm -f core conftest.err conftest.$ac_obj d30 1 a30 1 @@@@ -17014,6 +17019,10 @@@@ if test "$enable_pcretest_libreadline" = @ 1.8.22.1 log @Pullup ticket #4565 - requested by he devel/pcre: security update Revisions pulled up: - devel/pcre/Makefile 1.73,1.75 - devel/pcre/distinfo 1.54-1.55 - devel/pcre/patches/patch-CVE-2014-8964 1.1 - devel/pcre/patches/patch-aa 1.16 - devel/pcre/patches/patch-ab 1.9 --- Module Name: pkgsrc Committed By: wiz Date: Wed Oct 1 11:45:00 UTC 2014 Modified Files: pkgsrc/devel/pcre: Makefile distinfo Log Message: Update to 8.36: Version 8.36 26-September-2014 ------------------------------ 1. Got rid of some compiler warnings in the C++ modules that were shown up by -Wmissing-field-initializers and -Wunused-parameter. 2. The tests for quantifiers being too big (greater than 65535) were being applied after reading the number, and stupidly assuming that integer overflow would give a negative number. The tests are now applied as the numbers are read. 3. Tidy code in pcre_exec.c where two branches that used to be different are now the same. 4. The JIT compiler did not generate match limit checks for certain bracketed expressions with quantifiers. This may lead to exponential backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This issue should be resolved now. 5. Fixed an issue, which occures when nested alternatives are optimized with table jumps. 6. Inserted two casts and changed some ints to size_t in the light of some reported 64-bit compiler warnings (Bugzilla 1477). 7. Fixed a bug concerned with zero-minimum possessive groups that could match an empty string, which sometimes were behaving incorrectly in the interpreter (though correctly in the JIT matcher). This pcretest input is an example: '\A(?:[^"]++|"(?:[^"]*+|"")*+")++' NON QUOTED "QUOT""ED" AFTER "NOT MATCHED the interpreter was reporting a match of 'NON QUOTED ' only, whereas the JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test for an empty string was breaking the inner loop and carrying on at a lower level, when possessive repeated groups should always return to a higher level as they have no backtrack points in them. The empty string test now occurs at the outer level. 8. Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern ^\w+(?>\s*)(?<=\w) which caused it not to match "test test". 9. Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl doesn't). 10. Change 8.34/15 introduced a bug that caused the amount of memory needed to hold a pattern to be incorrectly computed (too small) when there were named back references to duplicated names. This could cause "internal error: code overflow" or "double free or corruption" or other memory handling errors. 11. When named subpatterns had the same prefixes, back references could be confused. For example, in this pattern: /(?Pa)?(?Pb)?(?()c|d)*l/ the reference to 'Name' was incorrectly treated as a reference to a duplicate name. 12. A pattern such as /^s?c/mi8 where the optional character has more than one "other case" was incorrectly compiled such that it would only try to match starting at "c". 13. When a pattern starting with \s was studied, VT was not included in the list of possible starting characters; this should have been part of the 8.34/18 patch. 14. If a character class started [\Qx]... where x is any character, the class was incorrectly terminated at the ]. 15. If a pattern that started with a caseless match for a character with more than one "other case" was studied, PCRE did not set up the starting code unit bit map for the list of possible characters. Now it does. This is an optimization improvement, not a bug fix. 16. The Unicode data tables have been updated to Unicode 7.0.0. 17. Fixed a number of memory leaks in pcregrep. 18. Avoid a compiler warning (from some compilers) for a function call with a cast that removes "const" from an lvalue by using an intermediate variable (to which the compiler does not object). 19. Incorrect code was compiled if a group that contained an internal recursive back reference was optional (had quantifier with a minimum of zero). This example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples caused segmentation faults because of stack overflows at compile time. 20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a group that is quantified with an indefinite repeat, caused a compile-time loop which used up all the system stack and provoked a segmentation fault. This was not the same bug as 19 above. 21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h. Patch by Mike Frysinger. --- Module Name: pkgsrc Committed By: spz Date: Sun Nov 30 14:48:43 UTC 2014 Modified Files: pkgsrc/devel/pcre: Makefile distinfo pkgsrc/devel/pcre/patches: patch-aa patch-ab Added Files: pkgsrc/devel/pcre/patches: patch-CVE-2014-8964 Log Message: patch for CVE-2014-8964 from upstream also, patch refresh @ text @d1 1 a1 1 $NetBSD$ d9 1 a9 1 --- configure.orig 2014-09-26 09:06:46.000000000 +0000 d11 1 a11 1 @@@@ -17603,6 +17603,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS d20 1 a20 1 @@@@ -17645,6 +17647,9 @@@@ rm -f core conftest.err conftest.$ac_obj d30 1 a30 1 @@@@ -18952,6 +18957,10 @@@@ elif test "$enable_pcretest_libreadline" @ 1.7 log @regen patches with better line numbers (no change) @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.6 2011/08/22 12:58:08 wiz Exp $ d11 1 a11 1 @@@@ -16189,6 +16189,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS d30 11 @ 1.6 log @Update to 8.13. Add comments to patches. Release 8.13 16-Aug-2011 ------------------------ This is mainly a bug-fix release. There has been a lot of internal refactoring. The Unicode tables have been updated. The only new feature in the library is the passing of *MARK information to callouts. Some additions have been made to pcretest to make testing easier and more comprehensive. There is a new option for pcregrep to adjust its internal buffer size. @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.5 2008/05/27 16:20:52 tnn Exp $ d9 1 a9 1 --- configure.orig 2008-05-07 18:22:58.000000000 +0200 d11 1 a11 1 @@@@ -20901,6 +20901,8 @@@@ ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS d20 1 a20 1 @@@@ -20968,6 +20970,9 @@@@ rm -f core conftest.err conftest.$ac_obj @ 1.5 log @Remove a feeble attempt at providing ABI compatibility for the C++ portion of the PCRE library. Relying on the C++ compiler to crunch symbols in a particular way is platform dependent at best, and the comments indicate that this was done for OSX. Also, the test misfired on SunOS leading to breakage (PR pkg/38768). I'm not bumping the ABI depends because I'm not aware of any packages using the C++ library. Bump PKGREVISION, however. @ text @d1 7 a7 1 $NetBSD$ @ 1.4 log @Update to 7.1: Release 7.1 24-Apr-07 --------------------- There is only one new feature in this release: a linebreak setting of PCRE_NEWLINE_ANYCRLF. It is a cut-down version of PCRE_NEWLINE_ANY, which recognizes only CRLF, CR, and LF as linebreaks. A few bugs are fixed (see ChangeLog for details), but the major change is a complete re-implementation of the build system. This now has full Autotools support and so is now "standard" in some sense. It should help with compiling PCRE in a wide variety of environments. NOTE: when building shared libraries for Windows, three dlls are now built, called libpcre, libpcreposix, and libpcrecpp. Previously, everything was included in a single dll. Another important change is that the dftables auxiliary program is no longer compiled and run at "make" time by default. Instead, a default set of character tables (assuming ASCII coding) is used. If you want to use dftables to generate the character tables as previously, add --enable-rebuild-chartables to the "configure" command. You must do this if you are compiling PCRE to run on a system that uses EBCDIC code. There is a discussion about character tables in the README file. The default is not to use dftables so that that there is no problem when cross-compiling. @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.3 2006/02/04 17:13:49 wiz Exp $ d3 5 a7 10 --- pcre-config.in.orig 2006-02-02 12:04:11.000000000 +0100 +++ pcre-config.in @@@@ -17,6 +17,9 @@@@ case `uname -s` in *SunOS*) libR=" -R@@libdir@@" ;; + *BSD*) + libR=" -Wl,-R@@libdir@@" + ;; esac d9 15 a23 1 while test $# -gt 0; do @ 1.3 log @Update to 6.5: Version 6.5 01-Feb-06 --------------------- 1. When using the partial match feature with pcre_dfa_exec(), it was not anchoring the second and subsequent partial matches at the new starting point. This could lead to incorrect results. For example, with the pattern /1234/, partially matching against "123" and then "a4" gave a match. 2. Changes to pcregrep: (a) All non-match returns from pcre_exec() were being treated as failures to match the line. Now, unless the error is PCRE_ERROR_NOMATCH, an error message is output. Some extra information is given for the PCRE_ERROR_MATCHLIMIT and PCRE_ERROR_RECURSIONLIMIT errors, which are probably the only errors that are likely to be caused by users (by specifying a regex that has nested indefinite repeats, for instance). If there are more than 20 of these errors, pcregrep is abandoned. (b) A binary zero was treated as data while matching, but terminated the output line if it was written out. This has been fixed: binary zeroes are now no different to any other data bytes. (c) Whichever of the LC_ALL or LC_CTYPE environment variables is set is used to set a locale for matching. The --locale=xxxx long option has been added (no short equivalent) to specify a locale explicitly on the pcregrep command, overriding the environment variables. (d) When -B was used with -n, some line numbers in the output were one less than they should have been. (e) Added the -o (--only-matching) option. (f) If -A or -C was used with -c (count only), some lines of context were accidentally printed for the final match. (g) Added the -H (--with-filename) option. (h) The combination of options -rh failed to suppress file names for files that were found from directory arguments. (i) Added the -D (--devices) and -d (--directories) options. (j) Added the -F (--fixed-strings) option. (k) Allow "-" to be used as a file name for -f as well as for a data file. (l) Added the --colo(u)r option. (m) Added Jeffrey Friedl's -S testing option, but within #ifdefs so that it is not present by default. 3. A nasty bug was discovered in the handling of recursive patterns, that is, items such as (?R) or (?1), when the recursion could match a number of alternatives. If it matched one of the alternatives, but subsequently, outside the recursion, there was a failure, the code tried to back up into the recursion. However, because of the way PCRE is implemented, this is not possible, and the result was an incorrect result from the match. In order to prevent this happening, the specification of recursion has been changed so that all such subpatterns are automatically treated as atomic groups. Thus, for example, (?R) is treated as if it were (?>(?R)). 4. I had overlooked the fact that, in some locales, there are characters for which isalpha() is true but neither isupper() nor islower() are true. In the fr_FR locale, for instance, the \xAA and \xBA characters (ordmasculine and ordfeminine) are like this. This affected the treatment of \w and \W when they appeared in character classes, but not when they appeared outside a character class. The bit map for "word" characters is now created separately from the results of isalnum() instead of just taking it from the upper, lower, and digit maps. (Plus the underscore character, of course.) 5. The above bug also affected the handling of POSIX character classes such as [[:alpha:]] and [[:alnum:]]. These do not have their own bit maps in PCRE's permanent tables. Instead, the bit maps for such a class were previously created as the appropriate unions of the upper, lower, and digit bitmaps. Now they are created by subtraction from the [[:word:]] class, which has its own bitmap. 6. The [[:blank:]] character class matches horizontal, but not vertical space. It is created by subtracting the vertical space characters (\x09, \x0a, \x0b, \x0c) from the [[:space:]] bitmap. Previously, however, the subtraction was done in the overall bitmap for a character class, meaning that a class such as [\x0c[:blank:]] was incorrect because \x0c would not be recognized. This bug has been fixed. 7. Patches from the folks at Google: (a) pcrecpp.cc: "to handle a corner case that may or may not happen in real life, but is still worth protecting against". (b) pcrecpp.cc: "corrects a bug when negative radixes are used with regular expressions". (c) pcre_scanner.cc: avoid use of std::count() because not all systems have it. (d) Split off pcrecpparg.h from pcrecpp.h and had the former built by "configure" and the latter not, in order to fix a problem somebody had with compiling the Arg class on HP-UX. (e) Improve the error-handling of the C++ wrapper a little bit. (f) New tests for checking recursion limiting. 8. The pcre_memmove() function, which is used only if the environment does not have a standard memmove() function (and is therefore rarely compiled), contained two bugs: (a) use of int instead of size_t, and (b) it was not returning a result (though PCRE never actually uses the result). 9. In the POSIX regexec() interface, if nmatch is specified as a ridiculously large number - greater than INT_MAX/(3*sizeof(int)) - REG_ESPACE is returned instead of calling malloc() with an overflowing number that would most likely cause subsequent chaos. 10. The debugging option of pcretest was not showing the NO_AUTO_CAPTURE flag. 11. The POSIX flag REG_NOSUB is now supported. When a pattern that was compiled with this option is matched, the nmatch and pmatch options of regexec() are ignored. 12. Added REG_UTF8 to the POSIX interface. This is not defined by POSIX, but is provided in case anyone wants to the the POSIX interface with UTF-8 strings. 13. Added CXXLDFLAGS to the Makefile parameters to provide settings only on the C++ linking (needed for some HP-UX environments). 14. Avoid compiler warnings in get_ucpname() when compiled without UCP support (unused parameter) and in the pcre_printint() function (omitted "default" switch label when the default is to do nothing). 15. Added some code to make it possible, when PCRE is compiled as a C++ library, to replace subject pointers for pcre_exec() with a smart pointer class, thus making it possible to process discontinuous strings. 16. The two macros PCRE_EXPORT and PCRE_DATA_SCOPE are confusing, and perform much the same function. They were added by different people who were trying to make PCRE easy to compile on non-Unix systems. It has been suggested that PCRE_EXPORT be abolished now that there is more automatic apparatus for compiling on Windows systems. I have therefore replaced it with PCRE_DATA_SCOPE. This is set automatically for Windows; if not set it defaults to "extern" for C or "extern C" for C++, which works fine on Unix-like systems. It is now possible to override the value of PCRE_DATA_ SCOPE with something explicit in config.h. In addition: (a) pcreposix.h still had just "extern" instead of either of these macros; I have replaced it with PCRE_DATA_SCOPE. (b) Functions such as _pcre_xclass(), which are internal to the library, but external in the C sense, all had PCRE_EXPORT in their definitions. This is apparently wrong for the Windows case, so I have removed it. (It makes no difference on Unix-like systems.) 17. Added a new limit, MATCH_LIMIT_RECURSION, which limits the depth of nesting of recursive calls to match(). This is different to MATCH_LIMIT because that limits the total number of calls to match(), not all of which increase the depth of recursion. Limiting the recursion depth limits the amount of stack (or heap if NO_RECURSE is set) that is used. The default can be set when PCRE is compiled, and changed at run time. A patch from Google adds this functionality to the C++ interface. 18. Changes to the handling of Unicode character properties: (a) Updated the table to Unicode 4.1.0. (b) Recognize characters that are not in the table as "Cn" (undefined). (c) I revised the way the table is implemented to a much improved format which includes recognition of ranges. It now supports the ranges that are defined in UnicodeData.txt, and it also amalgamates other characters into ranges. This has reduced the number of entries in the table from around 16,000 to around 3,000, thus reducing its size considerably. I realized I did not need to use a tree structure after all - a binary chop search is just as efficient. Having reduced the number of entries, I extended their size from 6 bytes to 8 bytes to allow for more data. (d) Added support for Unicode script names via properties such as \p{Han}. 19. In UTF-8 mode, a backslash followed by a non-Ascii character was not matching that character. 20. When matching a repeated Unicode property with a minimum greater than zero, (for example \pL{2,}), PCRE could look past the end of the subject if it reached it while seeking the minimum number of characters. This could happen only if some of the characters were more than one byte long, because there is a check for at least the minimum number of bytes. 21. Refactored the implementation of \p and \P so as to be more general, to allow for more different types of property in future. This has changed the compiled form incompatibly. Anybody with saved compiled patterns that use \p or \P will have to recompile them. 22. Added "Any" and "L&" to the supported property types. 23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode, but give a compile time error if the value is greater than 0xff. 24. The man pages for pcrepartial, pcreprecompile, and pcre_compile2 were accidentally not being installed or uninstalled. 25. The pcre.h file was built from pcre.h.in, but the only changes that were made were to insert the current release number. This seemed silly, because it made things harder for people building PCRE on systems that don't run "configure". I have turned pcre.h into a distributed file, no longer built by "configure", with the version identification directly included. There is no longer a pcre.h.in file. However, this change necessitated a change to the pcre-config script as well. It is built from pcre-config.in, and one of the substitutions was the release number. I have updated configure.ac so that ./configure now finds the release number by grepping pcre.h. 26. Added the ability to run the tests under valgrind. @ text @d1 1 a1 1 $NetBSD: patch-ab,v 1.2 2004/09/28 15:59:49 wiz Exp $ @ 1.2 log @Update to 5.0: Release 5.0 13-Sep-04 --------------------- The licence under which PCRE is released has been changed to the more conventional "BSD" licence. In the code, some bugs have been fixed, and there are also some major changes in this release (which is why I've increased the number to 5.0). Some changes are internal rearrangements, and some provide a number of new facilities. The new features are: 1. There's an "automatic callout" feature that inserts callouts before every item in the regex, and there's a new callout field that gives the position in the pattern - useful for debugging and tracing. 2. The extra_data structure can now be used to pass in a set of character tables at exec time. This is useful if compiled regex are saved and re-used at a later time when the tables may not be at the same address. If the default internal tables are used, the pointer saved with the compiled pattern is now set to NULL, which means that you don't need to do anything special unless you are using custom tables. 3. It is possible, with some restrictions on the content of the regex, to request "partial" matching. A special return code is given if all of the subject string matched part of the regex. This could be useful for testing an input field as it is being typed. 4. There is now some optional support for Unicode character properties, which means that the patterns items such as \p{Lu} and \X can now be used. Only the general category properties are supported. If PCRE is compiled with this support, an additional 90K data structure is include, which increases the size of the library dramatically. 5. There is support for saving compiled patterns and re-using them later. 6. There is support for running regular expressions that were compiled on a different host with the opposite endianness. 7. The pcretest program has been extended to accommodate the new features. The main internal rearrangement is that sequences of literal characters are no longer handled as strings. Instead, each character is handled on its own. This makes some UTF-8 handling easier, and makes the support of partial matching possible. Compiled patterns containing long literal strings will be larger as a result of this change; I hope that performance will not be much affected. @ text @d1 1 a1 1 $NetBSD$ d3 1 a3 1 --- pcre-config.in.orig 2004-09-13 16:20:00.000000000 +0200 @ 1.1 log @Add -Wl,-R... flags in pcre-config (same as we do for gtk-config). Bump pkg revision. @ text @d3 1 a3 1 --- pcre-config.in.orig Wed Jan 2 15:57:57 2002 d5 10 a14 13 @@@@ -45,10 +45,10 @@@@ while test $# -gt 0; do echo $includes ;; --libs-posix) - echo -L@@libdir@@ -lpcreposix -lpcre + echo -L@@libdir@@ -Wl,-R@@libdir@@ -lpcreposix -lpcre ;; --libs) - echo -L@@libdir@@ -lpcre + echo -L@@libdir@@ -Wl,-R@@libdir@@ -lpcre ;; *) echo "${usage}" 1>&2 @