Justin Mason wrote: > FWIW, this looks like it'd be excellent for SpamAssassin ;) > > I haven't had much time to look over the implementation, and I'm not > really any use for reviewing it from a p5p POV due to lack of familiarity > with perl internals, but the benchmark figures look fantastic and the > implementation details sound good.
I was waiting for Hugo's advice on this patch. Also, it would be nice to have something that works with /i, if that can be done reliably. > I'd love to see this get into perl, even if just as an option enabled > through a "use" pragma. (in my opinion, if your regexp will benefit > from a trie, you will know that in advance.) or a new end-of-regexp switch. But if it works well I don't see why this shouldn't be optimized by default (although avoiding slowdowns in some cases would even be better -- do they affect regexp compilation or execution ?)
