According to Dan Sugalski:
> Might as well go all the way, then--separate out the lexer/parser,
> the bit that turns the parsed syntax into an optree, the optimizer,
> and the backend that actually executes perl. Which, thinking about
> it, isn't that bad an idea [...]
This isn't new. It's pretty much pluggable right now in Perl 5 --
just make an XS that does what toke.c and perly.y do, maybe create a
hook for yyparse, and you're off.
The fact that people haven't used this opportunity may tell us
something. Or maybe not.
--
Chip Salzenberg - a.k.a. - <chip@valinux.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K