Jump to content
Sign in to follow this  
Guest Guest_NiTrogen_*

pcre 7.2?

Recommended Posts

Guest Guest_NiTrogen_*

Why using pcre 7.1?

Is 7.2 unstable?

Share this post

Link to post
Share on other sites

Why using pcre 7.1?

Is 7.2 unstable?

I am not looking at the evolution so I was not aware a new version come out. I will check

Share this post

Link to post
Share on other sites

Ooops, just realize that the latest version is 7.3.....;)

I will keep you updated :)

I notice too but I have some building problem the code does not compile under Windows VC8. I solve the config.h referencing I still have problem to build the .dll. Not sure we need but at least it is in our build process.

Stay tune. ;)

Share this post

Link to post
Share on other sites

7.3 version will be supported in


PS next time NitroGen don't use an open topic not related with your question. Thanks

Share this post

Link to post
Share on other sites

7.3 version will be supported in


PS next time NitroGen don't use an open topic not related with your question. Thanks

Hi jpm, 7.4 released

Version 7.4 21-Sep-07

1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
    means that a class such as [\s] counted as "explicit reference to CR or
    LF". That isn't really right - the whole point of the change was to try to
    help when there was an actual mention of one of the two characters. So now
    the change happens only if \r or \n (or a literal CR or LF) character is

2.  The 32-bit options word was also used for 6 internal flags, but the numbers
    of both had grown to the point where there were only 3 bits left.
    Fortunately, there was spare space in the data structure, and so I have
    moved the internal flags into a new 16-bit field to free up more option

3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
    but did not set the internal JCHANGED flag - either of these is enough to
    control the way the "get" function works - but the PCRE_INFO_JCHANGED
    facility is supposed to tell if (?J) was ever used, so now (?J) at the
    start sets both bits.

4.  Added options (at build time, compile time, exec time) to change \R from
    matching any Unicode line ending sequence to just matching CR, LF, or CRLF.

5.  doc/pcresyntax.html was missing from the distribution.

6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
    compatibility, even though it is no longer used.

7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
    strtoull to pcrecpp.cc to select the available functions in WIN32 when the
    windows.h file is present (where different names are used). [This was
    reversed later after testing - see 16 below.]

8.  Changed all #include <config.h> to #include "config.h". There were also
    some further <pcre.h> cases that I changed to "pcre.h".

9.  When pcregrep was used with the --colour option, it missed the line ending
    sequence off the lines that it output.

10. It was pointed out to me that arrays of string pointers cause lots of
    relocations when a shared library is dynamically loaded. A technique of
    using a single long string with a table of offsets can drastically reduce
    these. I have refactored PCRE in four places to do this. The result is

      Originally:                         290
      After changing UCP table:         187
      After changing error message table:   43
      After changing table of "verbs"      36
      After changing table of Posix names   22

    Thanks to the folks working on Gregex for glib for this insight.

11. --disable-stack-for-recursion caused compiling to fail unless -enable-
    unicode-properties was also set.

12. Updated the tests so that they work when \R is defaulted to ANYCRLF.

13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
    checked only for CRLF.

14. Added casts to pcretest.c to avoid compiler warnings.

15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.

16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
    and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
    entirely. This removes changes made in 7 above.

17. The CMake files have been updated, and there is now more information about
    building with CMake in the NON-UNIX-USE document.

Share this post

Link to post
Share on other sites

Version 7.5 10-Jan-08


1. Applied a patch from Craig: "This patch makes it possible to 'ignore'

values in parens when parsing an RE using the C++ wrapper."

2. Negative specials like \S did not work in character classes in UTF-8 mode.

Characters greater than 255 were excluded from the class instead of being


3. The same bug as (2) above applied to negated POSIX classes such as


4. PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it

defined or documented. It seems to have been a typo for PCRE_STATIC, so

I have changed it.

5. The construct (?&) was not diagnosed as a syntax error (it referenced the

first named subpattern) and a construct such as (?&a) would reference the

first named subpattern whose name started with "a" (in other words, the

length check was missing). Both these problems are fixed. "Subpattern name

expected" is now given for (?&) (a zero-length name), and this patch also

makes it give the same error for \k'' (previously it complained that that

was a reference to a non-existent subpattern).

6. The erroneous patterns (?+-a) and (?-+a) give different error messages;

this is right because (?- can be followed by option settings as well as by

digits. I have, however, made the messages clearer.

7. Patterns such as (?(1)a|:) (a pattern that contains fewer subpatterns

than the number used in the conditional) now cause a compile-time error.

This is actually not compatible with Perl, which accepts such patterns, but

treats the conditional as always being FALSE (as PCRE used to), but it

seems to me that giving a diagnostic is better.

8. Change "alphameric" to the more common word "alphanumeric" in comments

and messages.

9. Fix two occurrences of "backslash" in comments that should have been


10. Remove two redundant lines of code that can never be obeyed (their function

was moved elsewhere).

11. The program that makes PCRE's Unicode character property table had a bug

which caused it to generate incorrect table entries for sequences of

characters that have the same character type, but are in different scripts.

It amalgamated them into a single range, with the script of the first of

them. In other words, some characters were in the wrong script. There were

thirteen such cases, affecting characters in the following ranges:

U+002b0 - U+002c1

U+0060c - U+0060d

U+0061e - U+00612

U+0064b - U+0065e

U+0074d - U+0076d

U+01800 - U+01805

U+01d00 - U+01d77

U+01d9b - U+01dbf

U+0200b - U+0200f

U+030fc - U+030fe

U+03260 - U+0327f

U+0fb46 - U+0fbb1

U+10450 - U+1049d

12. The -o option (show only the matching part of a line) for pcregrep was not

compatible with GNU grep in that, if there was more than one match in a

line, it showed only the first of them. It now behaves in the same way as

GNU grep.

13. If the -o and -v options were combined for pcregrep, it printed a blank

line for every non-matching line. GNU grep prints nothing, and pcregrep now

does the same. The return code can be used to tell if there were any

non-matching lines.

14. Added --file-offsets and --line-offsets to pcregrep.

15. The pattern (?=something)(?R) was not being diagnosed as a potentially

infinitely looping recursion. The bug was that positive lookaheads were not

being skipped when checking for a possible empty match (negative lookaheads

and both kinds of lookbehind were skipped).

16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the

inclusion of <windows.h> to before rather than after the definition of

INVALID_FILE_ATTRIBUTES (patch from David Byron).

17. Specifying a possessive quantifier with a specific limit for a Unicode

character property caused pcre_compile() to compile bad code, which led at

runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this

are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that

caused the error; without that there was no problem.

18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.

19. Added --enable-pcretest-libreadline.

20. In pcrecpp.cc, the variable 'count' was incremented twice in

RE::GlobalReplace(). As a result, the number of replacements returned was

double what it should be. I removed one of the increments, but Craig sent a

later patch that removed the other one (the right fix) and added unit tests

that check the return values (which was not done before).

21. Several CMake things:

(1) Arranged that, when cmake is used on Unix, the libraries end up with

the names libpcre and libpcreposix, not just pcre and pcreposix.

(2) The above change means that pcretest and pcregrep are now correctly

linked with the newly-built libraries, not previously installed ones.


22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*

crashed when matching a string such as a\x{2029}b (note that \x{2029} is a

UTF-8 newline character). The key issue is that the pattern starts .*;

this means that the match must be either at the beginning, or after a

newline. The bug was in the code for advancing after a failed match and

checking that the new position followed a newline. It was not taking

account of UTF-8 characters correctly.

23. PCRE was behaving differently from Perl in the way it recognized POSIX

character classes. PCRE was not treating the sequence [:...:] as a

character class unless the ... were all letters. Perl, however, seems to

allow any characters between [: and :], though of course it rejects as

unknown any "names" that contain non-letters, because all the known class

names consist only of letters. Thus, Perl gives an error for [[:1234:]],

for example, whereas PCRE did not - it did not recognize a POSIX character

class. This seemed a bit dangerous, so the code has been changed to be

closer to Perl. The behaviour is not identical to Perl, because PCRE will

diagnose an unknown class for, for example, [[:l\ower:]] where Perl will

treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where

Perl does, and where it didn't before.

24. Rewrite so as to remove the single use of %n from pcregrep because in some

Windows environments %n is disabled by default.

Share this post

Link to post
Share on other sites

Version 7.6 28-Jan-08


1. A character class containing a very large number of characters with

codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer


2. Patch to cut out the "long long" test in pcrecpp_unittest when

HAVE_LONG_LONG is not defined.

3. Applied Christian Ehrlicher's patch to update the CMake build files to

bring them up to date and include new features. This patch includes:

- Fixed PH's badly added libz and libbz2 support.

- Fixed a problem with static linking.

- Added pcredemo. [but later removed - see 7 below.]

- Fixed dftables problem and added an option.

- Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and


- Added readline support for pcretest.

- Added an listing of the option settings after cmake has run.

4. A user submitted a patch to Makefile that makes it easy to create

"pcre.dll" under mingw when using Configure/Make. I added stuff to

Makefile.am that cause it to include this special target, without

affecting anything else. Note that the same mingw target plus all

the other distribution libraries and programs are now supported

when configuring with CMake (see 6 below) instead of with


5. Applied Craig's patch that moves no_arg into the RE class in the C++ code.

This is an attempt to solve the reported problem "pcrecpp::no_arg is not

exported in the Windows port". It has not yet been confirmed that the patch

solves the problem, but it does no harm.

6. Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and

NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured

with CMake, and also correct the comment about stack recursion.

7. Remove the automatic building of pcredemo from the ./configure system and

from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example

of a program that users should build themselves after PCRE is installed, so

building it automatically is not really right. What is more, it gave

trouble in some build environments.

8. Further tidies to CMakeLists.txt from Sheri and Christian.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...