Jay Berkenbilt wrote:

I can look into this
in more depth to see whether one is required or not.  There's a good
chance there won't be even though 5.0 supports many more Unicode
properties.

From a five minute look through the header files, I don't believe that a new soname is required. It seems to be quite well designed for compatibility. Please tell me if you think otherwise.

Probably all old interfaces still work and do the same
thing.  Some constructs that were formerly invalid will be valid now,
and there may be some more values that can be orred into the option
flags, but hopefully that's the end of it.

It pretty much looks like it to me.

Since pcre3 is standard, I'm guessing this won't be approved for sarge
anyway.


I don't intend to try to get it into sarge.

Sorry I didn't notice this when it came out back in September, by the way. I thought I was on the pcre mailing list, but obviously I'm not, and indeed there doesn't appear to be one.




-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to