Dan Sugalski wrote: > 1) How fast is the C (or whatever) code it emits likely to be? The perl-in-perl interpreter would not be a deliverable. Speed would not be its goal. It would be a reference implementation that would be easier to break and repair. An internals tutorial, if you will. So you don't have to go explaining what you mean by "vtable" freshly to every new person who figures it out on their own and gets it subtly wrong, for instance. It's a documentation exercise, the serious implementors would port it to the target language and would raise hell when something difficult to port shows up in it. -- David Nicol 816.235.1187 [EMAIL PROTECTED] perl -e'map{sleep print$w[rand@w]}@w=<>' ~/nsmail/Inbox
- 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