On Tue, 27 Aug 2002, Steve Fink wrote: > For those following along at home: regex engines seem to be too much > fun for people to resist. I know of at least 5 parsers, 4 compilers, > and 5 backend op sets that have been written over the course of the > Parrot project: > > Parsers: > - My languages/regex/lib/Regex/Grammar.y (only perl5 re's, crappy) > - Jeff's languages/perl6re.bnf > - Didn't Sean have another one?
Yes -- the one that's being used by P6C starts at line 700 in Parser.pm. It's pretty clean, and could stand apart from the rest of the grammar with a few tweaks, if anyone wants to use it. > Backend ops: > - Brent's original rx ops > - The rx ops with Angel's modifications > - My abandoned implicitly backtracking re ops Are these abandoned for good, or just for the moment? > - Plain pasm ops > - Simon Cozen's tree walkers > > Many of these fed off of each other. Brent Dax's rx.ops documentation > gave both Sean and me the initial start on explicit backtracking code > generation, Thanks, Brent. > Sean and I discuss implementation ideas a little, and I think some > more happens on IRC that I don't know about. Actually, there's hardly any irc discussion of regexes -- us regex re-implementors seem to suffer from a failure to communicate... > Currently, Sean's stuff is very well integrated with perl6; my stuff > is pretty much ignored; s/well/tightly/. After 0.0.8, I'm planning on taking a much more serious look at Steve's stuff. I'm hoping that, with the right interface there will be very little overhead in sticking externally-created bits into Steve's regexes. > And I'm not sure why I just wrote all that up. Well, thanks anyways for getting all carried away like that. /s
