[erlang-questions] regexp sux!
Sun May 20 14:14:45 CEST 2007
My ordered wishlist:
1. Being able to extract submatches, like gregexp
2. Matching over binaries without binary_to_list
3. Being able to control greedy vs non-greedy matching
4. A syntax transform that transforms regexps into a calls to
generated erlang functions
that implement the regexp. (Iff this make regexps faster :)
On 5/20/07, Robert Virding <> wrote:
> A few comments about that seeing it is my fault. :-) Anchoring, ^ and $,
> doesn't work when compiling the regexp with compile, but it should work
> when running it directly or with just parse. If it doesn't then it is bug.
> I am working on some new regexp modules with both POSIX and PERL style
> regexps. There will probably be two modules as they don't just have
> different features but also different semantics, they will find
> different matches.
> What features are people mainly interested in? What should I focus on to
> start with?
> N.B. I am implementing it all in Erlang and not doing an interface to a
> "C" library like PCRE. I mean where's the fun in that?
> Luke Gorrie wrote:
> > Robert Virding <> writes:
> >> There is a new version of regexp in the pipe which:
> > Today I'm in the market for a fast regexp matcher so please send me a
> > copy if you have it handy :-)
> > I had a quick look at the one on trapexit but it crashed on the regexp
> > "^x" in build_nfa (a missing clause).
> > BTW years ago I ported the OTP Erlang regexp matcher to Haskell and
> > John Hughes immediately found a bug with Quickcheck. Now that
> > Quickcheck exists for Erlang too the OTP folks might find it handy.
> > Unfortunately this was on an infernal "Yahoo! Groups" forum and
> > it seems to have garbage collected the source code.
> > _______________________________________________
> > erlang-questions mailing list
> > http://www.erlang.org/mailman/listinfo/erlang-questions
> erlang-questions mailing list
More information about the erlang-questions