Dan Sugalski wrote: > As for the language we implement perl in (and thus ultimately need to > translate to the compiler-target language), I'm thinking of something like > Chip's PIL. That's fine for the VM and the support libraries, but I'd *really* like to see the parser/front-end in Perl. There are dozens of RFCs that require some non-trivial extensions to the parser. It would be nice to code these in Perl -- especially if we can co-evolve the regex engine to support the extensions. I think this would also help us document the interface between the front-end and back-end (which could be a compiler or the VM). IMHO this separation is worth it even if it costs us some performance. - Ken
- Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language David L. Nicol
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language Simon Cozens
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language Simon Cozens
- Re: Perl Implementation Langua... Dan Sugalski
- Re: Perl Implementation La... Simon Cozens
- Re: Perl Implementation Language David L. Nicol
- Re: Perl Implementation Language Joshua N Pritikin
- Re: Perl Implementation Language Ken Fox
- Re: Perl Implementation Language Simon Cozens
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language Simon Cozens
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language Bradley M. Kuhn
- Re: Perl Implementation Language Ken Fox
- Re: Perl Implementation Language Nathan Torkington
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Langua... Philip Newton
- No, not A, but A David L. Nicol