On Wed, Apr 25, 2007 at 06:20:55PM +0100, Jonathan Worthington wrote: > Allison Randal wrote: > >Nicholas Clark wrote: > >> > >>I guess that the most obvious current thing that ties Parrot to the Perl > >>community is that Parrot requires a copy of Perl to bootstrap, and > >>all the > >>build tools are written in Perl 5. > >This is slated to change before the 1.0 release. > I guess that doing so will involve re-writing a lot of the current > Configure system and build tools into something that compiles down to > PBC (and then just ship something very basic that can run a PBC). I > don't think PIR is the thing to translate them to though - Configure and > the build tools are fairly big things. You don't want to be doing that > in an intermediate language. Well, I sure don't anyway, and I'm sure I'm > not alone in feeling this way.
I believe that the intent, or at least my intent, was for the Perl5 cod to be compiled down to PBC that was shipped with the distribution to be executed via miniparrot. Of course, configuring miniparrot without "Configure" is an unsolved problem. -J --
pgp8tY3fuvJhP.pgp
Description: PGP signature
