For me it's definitely a blocker and I guess it would be the same for
some users.
But, if you can choose your RE engine that would be a perfect solution
(as far as you compile it yourself).
Furtermore, if the UTF-8 support is better in another library, we could
try it also.
Marc
On 4/5/16, 1:53 AM, "Christian Folini" <chr...@ne...> wrote:
> If you need features (e.g. sub-expression capture) or pattern
> constructs
> (e.g. back-references or arbitrary look around asserts) you may not be
> able to use Hyperscan (although we do have a pre-filter mode that can
> optimize some cases).
> ->http://scanmail.trustwave.com/?c=4062&d=_8SD17SSFxcGTyITZx90bheVWxEf38or3BaqDWrOIQ&s=5&u=https%3a%2f%2f01%2eorg%2fhyperscan%2fblogs%2fgeofflangdale%2f2015%2fwelcome-hyperscan
>
> Is not that a blocker?
It is not clear to me if this is a blocker. I don't think so. Are you concerned
about the sub-expression capture?
It is also not clear if it will really improve the performance, as our content
is usually very small. I guess it is not so hard to test.
|
