Re: [pcre-dev] Using the Google C++ PCRE code

2014-11-11 Thread Matthew Hall
On Tue, Nov 11, 2014 at 03:04:06PM +, Callanan, Colin C. wrote: I also noticed that we had been using the google C++ wrapper code, as seen in pcrecpp.h: Depending what you're doing if you want to use C++ and you are getting performance issues like it sounds like you were partly having you

Re: [pcre-dev] Using the Google C++ PCRE code

2014-11-11 Thread Ze'ev Atlas
Matthew wrote I just wrote some code of my own which lets you switch between both libs and it wasn't too hard to make it work with each one at once as the API's (in C) were not too different. Could you generalize and publish that code, please Ze'ev Atlas -- ## List details at

Re: [pcre-dev] Using the Google C++ PCRE code

2014-11-11 Thread Matthew Hall
On Tue, Nov 11, 2014 at 11:47:44AM -0800, Ze'ev Atlas wrote: Matthew wrote I just wrote some code of my own which lets you switch between both libs and it wasn't too hard to make it work with each one at once as the API's (in C) were not too different. Could you generalize and publish

Re: [pcre-dev] Using the Google C++ PCRE code

2014-11-11 Thread Zoltán Herczeg
Hi, It has almost as many matching features as PCRE with same syntax, and is guaranteed non-backtracking with linear time performance in the length of the input. Hm, not exactly. Re2 never said that. They have a list of available features, and the more interesting ones are all grayed out: