Re: [pcre-dev] \K in lookahead assertion gives unpredictable result

2013-12-24 Thread Zoltán Herczeg
Hi, Anyway I suspect the result is correct (it start with b) I don't think so. Result must not have 'b'. Did you see my other mail yesterday? I explained there that pcretest yields 'b' for testing purposes (it handles startoffset is greater than endoffset cases this way). I also described

Re: [pcre-dev] \K in lookahead assertion gives unpredictable result

2013-12-24 Thread ph10
On Mon, 23 Dec 2013, ND wrote: It seems that last PCRE version have this problem too: I have not looked at this yet, and as I have visiting family over the holiday period, I may not get a chance till next week. Grandchildren are fun, but hard work. Philip -- Philip Hazel -- ## List

Re: [pcre-dev] [Bug 1419] PCRE slower at matching UTF8 character classes.

2013-12-24 Thread ph10
On Sun, 22 Dec 2013, Ze'ev Atlas wrote: I know that this change make no difference in my port and I agree that such a massive change would require a new version number (despite the prior anticipation that 8.34 would be the last 8.xx version.) I am hoping to get back to working on the new API

Re: [pcre-dev] PCRE 8.34 is released

2013-12-24 Thread ph10
On Mon, 16 Dec 2013, Petr Pisar wrote: However GCC 4.8.2 emits new warnings (CFLAGS='-O2 -g -pipe -Wall I have GCC 4.8.2, but annoyingly these warnings happen only with -O2, and I was doing all my testing with -O0 to save time. I have now fixed these warnings, and arranged that at least one