Dan Sugalski <[EMAIL PROTECTED]> wrote:
> It's more than just the parser. You've got the bytecode compiler and
> possibly the optimizer as well, and they're probably going to be all, or
> mostly, C. On the other hand they might not have any internal hooks for
> perl code to wedge into, in which c
At 06:28 PM 12/2/00 -0500, Bradley M. Kuhn wrote:
>Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> > It's more than just the parser. You've got the bytecode compiler and
> > possibly the optimizer as well, and they're probably going to be all, or
> > mostly, C. On the other hand they might not have an
