Update to 4.4:

 1. In UTF-8 mode, a character class containing characters with values between
    127 and 255 was not handled correctly if the compiled pattern was studied.
    In fixing this, I have also improved the studying algorithm for such
    classes (slightly).

 2. Three internal functions had redundant arguments passed to them. Removal
    might give a very teeny performance improvement.

 3. Documentation bug: the value of the capture_top field in a callout is *one
    more than* the number of the hightest numbered captured substring.

 4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
    in incorrectly linking with a previously installed version. They now link
    explicitly with libpcre.la.

 5. configure.in no longer needs to recognize Cygwin specially.

 6. A problem in pcre.in for Windows platforms is fixed.

 7. If a pattern was successfully studied, and the -d (or /D) flag was given to
    pcretest, it used to include the size of the study block as part of its
    output. Unfortunately, the structure contains a field that has a different
    size on different hardware architectures. This meant that the tests that
    showed this size failed. As the block is currently always of a fixed size,
    this information isn't actually particularly useful in pcretest output, so
    I have just removed it.

 8. Three pre-processor statements accidentally did not start in column 1.
    Sadly, there are *still* compilers around that complain, even though
    standard C has not required this for well over a decade. Sigh.

 9. In pcretest, the code for checking callouts passed small integers in the
    callout_data field, which is a void * field. However, some picky compilers
    complained about the casts involved for this on 64-bit systems. Now
    pcretest passes the address of the small integer instead, which should get
    rid of the warnings.

10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
    both compile and run time, and gives an error if an invalid UTF-8 sequence
    is found. There is a option for disabling this check in cases where the
    string is known to be correct and/or the maximum performance is wanted.

11. In response to a bug report, I changed one line in Makefile.in from

        -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
    to
        -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \

    to look similar to other lines, but I have no way of telling whether this
    is the right thing to do, as I do not use Windows. No doubt I'll get told
    if it's wrong...

2 files changed, 5 insertions, 5 deletions

diff --git a/devel/pcre/Makefile b/devel/pcre/Makefile
index 41b0c428dc8..42dd1314cf7 100644
--- a/devel/pcre/Makefile
+++ b/devel/pcre/Makefile
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.14 2003/08/05 10:18:39 wiz Exp $
+# $NetBSD: Makefile,v 1.15 2003/08/31 11:28:48 wiz Exp $
 # FreeBSD Id: Makefile,v 1.1.1.1 1998/07/12 22:59:19 steve Exp $
 
-DISTNAME=	pcre-4.3
+DISTNAME=	pcre-4.4
 CATEGORIES=	devel
 MASTER_SITES=	ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/	\
 		ftp://pcre.sourceforge.net/pub/pcre/
diff --git a/devel/pcre/distinfo b/devel/pcre/distinfo
index a298e0ed7b9..17841c8d8d3 100644
--- a/devel/pcre/distinfo
+++ b/devel/pcre/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.8 2003/08/05 10:18:40 wiz Exp $
+$NetBSD: distinfo,v 1.9 2003/08/31 11:28:49 wiz Exp $
 
-SHA1 (pcre-4.3.tar.bz2) = 8ac56705c620b605fc475d5ee975c395230b356d
-Size (pcre-4.3.tar.bz2) = 337382 bytes
+SHA1 (pcre-4.4.tar.bz2) = ee7a50d5de4bf71d575bb3db03d319b017a6c8c0
+Size (pcre-4.4.tar.bz2) = 341388 bytes
 SHA1 (patch-aa) = 4c11a0397ee40f42b9bc809c84050b63b2fee2fb
 SHA1 (patch-ab) = 03bb38f5d07964a5ab16b1c80538ac77b3625640