Steve Fink:
# I've written a more or less working regular expression compiler and
# optimizer.
Excellent work!
# Where should I put it? It's not really part of Parrot, at
# least no more than perl's eval"" would be. Would languages/regex be ok
# for now?
We have an opcode, rx_compile, slotted for a generic regex compiler.
The idea is that most regex-heavy languages (like Perl) would implement
their own compilers with the extra semantics necessary, but many
languages that don't need advanced features can use the built-in.
(Advanced features are things like (?{}), named groups (e.g. Microsoft's
(?<name>regex) syntax), certain switches for things like
accent-insensitive matches, etc.) If it's in C, put it into an
rxcomp.c/rxcomp.h and make rx_compile call it. If it's not, well, I'm
not sure what to do about that. Port it to Parrot bytecode, perhaps?
:^)
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking, regex hacker, embedding coder, and boy genius
#define private public
--Spotted in a C++ program just before a #include
