On Fri, 15 Sep 2000, Dan Sugalski wrote: > Doing core work in perl also has startup issues--either we need to parse > perl code every time perl starts, write the optree stuff to be > position-independent, compile perl down to native code, or embed and > process bytecode every time we start. I don't quite buy the dogfoog argument. Use the best tool for the job (or, at least, a decent one). This brings to mind the quote from perlfaq1 under "When shouldn't I program in Perl?": "You'll notice that perl itself is not written in Perl. (Though it might be interesting to reread the whole paragraph.) Cheers, Philip -- Philip Newton <[EMAIL PROTECTED]>
- 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
- No, not A, but A Philip Newton
- No, not A, but A David L. Nicol
- Re: Perl Implementation Language Piers Cawley
- 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 Language raptor
- Re: Perl Implementation Language Dan Sugalski
- Re: Perl Implementation Language Tom Hughes
- Re: Perl Implementation Language Dan Sugalski