Import of PCRE 3.9

University of Cambridge Computing Service,

Cambridge, England. Phone: +44 1223 334714.

Copyright (c) 1997-2000 University of Cambridge

Copyright (c) 1997-2001 University of Cambridge

University of Cambridge Computing Service,

Cambridge, England. Phone: +44 1223 334714.

Copyright (c) 1997-2000 University of Cambridge

Copyright (c) 1997-2001 University of Cambridge

Permission is granted to anyone to use this software for any purpose on any

computer system, and to redistribute it freely, subject to the following

   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

2. The origin of this software must not be misrepresented, either by

   explicit claim or by omission.

   explicit claim or by omission. In practice, this means that if you use

   PCRE in software which you distribute to others, commercially or

   otherwise, you must put a sentence like this

     Regular expression support is provided by the PCRE library package,

     which is open source software, written by Philip Hazel, and copyright

     by the University of Cambridge, England.

   somewhere reasonably visible in your documentation and in any relevant

   files or online help data or similar. A reference to the ftp site for

   the source, that is, to

     ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

   should also be given in the documentation.

3. Altered versions must be plainly marked as such, and must not be

   misrepresented as being the original software.

4. If PCRE is embedded in any software that is released under the GNU

   General Purpose Licence (GPL), then the terms of that licence shall

   supersede any condition above with which it is incompatible.

   General Purpose Licence (GPL), or Lesser General Purpose Licence (LGPL),

   then the terms of that licence shall supersede any condition above with

   which it is incompatible.

The documentation for PCRE, supplied in the "doc" directory, is distributed

under the same terms as the software itself.

End

ChangeLog for PCRE

------------------

Version 3.0 02-Jan-02

---------------------

1. A bit of extraneous text had somehow crept into the pcregrep documentation.

2. If --disable-static was given, the building process failed when trying to

build pcretest and pcregrep. (For some reason it was using libtool to compile

them, which is not right, as they aren't part of the library.)

Version 3.8 18-Dec-01

---------------------

1. The experimental UTF-8 code was completely screwed up. It was packing the

bytes in the wrong order. How dumb can you get?

Version 3.7 29-Oct-01

---------------------

1. In updating pcretest to check change 1 of version 3.6, I screwed up.

This caused pcretest, when used on the test data, to segfault. Unfortunately,

this didn't happen under Solaris 8, where I normally test things.

2. The Makefile had to be changed to make it work on BSD systems, where 'make'

doesn't seem to recognize that ./xxx and xxx are the same file. (This entry

isn't in ChangeLog distributed with 3.7 because I forgot when I hastily made

this fix an hour or so after the initial 3.7 release.)

Version 3.6 23-Oct-01

---------------------

1. Crashed with /(sens|respons)e and \1ibility/ and "sense and sensibility" if

offsets passed as NULL with zero offset count.

2. The config.guess and config.sub files had not been updated when I moved to

the latest autoconf.

Version 3.5 15-Aug-01

---------------------

1. Added some missing #if !defined NOPOSIX conditionals in pcretest.c that

had been forgotten.

2. By using declared but undefined structures, we can avoid using "void"

definitions in pcre.h while keeping the internal definitions of the structures

private.

3. The distribution is now built using autoconf 2.50 and libtool 1.4. From a

user point of view, this means that both static and shared libraries are built

by default, but this can be individually controlled. More of the work of

handling this static/shared cases is now inside libtool instead of PCRE's make

file.

4. The pcretest utility is now installed along with pcregrep because it is

useful for users (to test regexs) and by doing this, it automatically gets

relinked by libtool. The documentation has been turned into a man page, so

there are now .1, .txt, and .html versions in /doc.

5. Upgrades to pcregrep:

   (i)   Added long-form option names like gnu grep.

   (ii)  Added --help to list all options with an explanatory phrase.

   (iii) Added -r, --recursive to recurse into sub-directories.

   (iv)  Added -f, --file to read patterns from a file.

6. pcre_exec() was referring to its "code" argument before testing that

argument for NULL (and giving an error if it was NULL).

7. Upgraded Makefile.in to allow for compiling in a different directory from

the source directory.

8. Tiny buglet in pcretest: when pcre_fullinfo() was called to retrieve the

options bits, the pointer it was passed was to an int instead of to an unsigned

long int. This mattered only on 64-bit systems.

9. Fixed typo (3.4/1) in pcre.h again. Sigh. I had changed pcre.h (which is

generated) instead of pcre.in, which it its source. Also made the same change

in several of the .c files.

10. A new release of gcc defines printf() as a macro, which broke pcretest

because it had an ifdef in the middle of a string argument for printf(). Fixed

by using separate calls to printf().

11. Added --enable-newline-is-cr and --enable-newline-is-lf to the configure

script, to force use of CR or LF instead of \n in the source. On non-Unix

systems, the value can be set in config.h.

12. The limit of 200 on non-capturing parentheses is a _nesting_ limit, not an

absolute limit. Changed the text of the error message to make this clear, and

likewise updated the man page.

13. The limit of 99 on the number of capturing subpatterns has been removed.

The new limit is 65535, which I hope will not be a "real" limit.

Version 3.4 22-Aug-00

---------------------

1. Fixed typo in pcre.h: unsigned const char * changed to const unsigned char *.

2. Diagnose condition (?(0) as an error instead of crashing on matching.

Version 3.3 01-Aug-00

---------------------

1. If an octal character was given, but the value was greater than \377, it

was not getting masked to the least significant bits, as documented. This could

lead to crashes in some systems.

2. Perl 5.6 (if not earlier versions) accepts classes like [a-\d] and treats

the hyphen as a literal. PCRE used to give an error; it now behaves like Perl.

3. Added the functions pcre_free_substring() and pcre_free_substring_list().

These just pass their arguments on to (pcre_free)(), but they are provided

because some uses of PCRE bind it to non-C systems that can call its functions,

but cannot call free() or pcre_free() directly.

4. Add "make test" as a synonym for "make check". Corrected some comments in

the Makefile.

5. Add $(DESTDIR)/ in front of all the paths in the "install" target in the

Makefile.

6. Changed the name of pgrep to pcregrep, because Solaris has introduced a

command called pgrep for grepping around the active processes.

7. Added the beginnings of support for UTF-8 character strings.

8. Arranged for the Makefile to pass over the settings of CC, CFLAGS, and

RANLIB to ./ltconfig so that they are used by libtool. I think these are all

the relevant ones. (AR is not passed because ./ltconfig does its own figuring

out for the ar command.)

Version 3.2 12-May-00

---------------------

This is purely a bug fixing release.

1. If the pattern /((Z)+|A)*/ was matched agained ZABCDEFG it matched Z instead

of ZA. This was just one example of several cases that could provoke this bug,

which was introduced by change 9 of version 2.00. The code for breaking

infinite loops after an iteration that matches an empty string was't working

correctly.

2. The pcretest program was not imitating Perl correctly for the pattern /a*/g

when matched against abbab (for example). After matching an empty string, it

wasn't forcing anchoring when setting PCRE_NOTEMPTY for the next attempt; this

caused it to match further down the string than it should.

3. The code contained an inclusion of sys/types.h. It isn't clear why this

was there because it doesn't seem to be needed, and it causes trouble on some

systems, as it is not a Standard C header. It has been removed.

4. Made 4 silly changes to the source to avoid stupid compiler warnings that

were reported on the Macintosh. The changes were from

  while ((c = *(++ptr)) != 0 && c != '\n');

to

  while ((c = *(++ptr)) != 0 && c != '\n') ;

Totally extraordinary, but if that's what it takes...

5. PCRE is being used in one environment where neither memmove() nor bcopy() is

available. Added HAVE_BCOPY and an autoconf test for it; if neither

HAVE_MEMMOVE nor HAVE_BCOPY is set, use a built-in emulation function which

assumes the way PCRE uses memmove() (always moving upwards).

6. PCRE is being used in one environment where strchr() is not available. There

was only one use in pcre.c, and writing it out to avoid strchr() probably gives

faster code anyway.

Version 3.1 09-Feb-00

---------------------

   These are generic installation instructions that apply to systems that

can run the `configure' shell script - Unix systems and any that imitate

it. They are not specific to PCRE. There are PCRE-specific instructions

for non-Unix systems in the file NON-UNIX.

for non-Unix systems in the file NON-UNIX-USE.

   The `configure' shell script attempts to guess correct values for

various system-dependent variables used during compilation.  It uses

University of Cambridge Computing Service,

Cambridge, England. Phone: +44 1223 334714.

Copyright (c) 1997-2000 University of Cambridge

Copyright (c) 1997-2001 University of Cambridge

Permission is granted to anyone to use this software for any purpose on any

computer system, and to redistribute it freely, subject to the following

   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

2. The origin of this software must not be misrepresented, either by

   explicit claim or by omission.

   explicit claim or by omission. In practice, this means that if you use

   PCRE in software which you distribute to others, commercially or

   otherwise, you must put a sentence like this

     Regular expression support is provided by the PCRE library package,

     which is open source software, written by Philip Hazel, and copyright

     by the University of Cambridge, England.

   somewhere reasonably visible in your documentation and in any relevant

   files or online help data or similar. A reference to the ftp site for

   the source, that is, to

     ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

   should also be given in the documentation.

3. Altered versions must be plainly marked as such, and must not be

   misrepresented as being the original software.

4. If PCRE is embedded in any software that is released under the GNU

   General Purpose Licence (GPL), then the terms of that licence shall

   supersede any condition above with which it is incompatible.

   General Purpose Licence (GPL), or Lesser General Purpose Licence (LGPL),

   then the terms of that licence shall supersede any condition above with

   which it is incompatible.

The documentation for PCRE, supplied in the "doc" directory, is distributed

under the same terms as the software itself.

End