On 27 Jun 2005, at 15:47, [EMAIL PROTECTED] wrote:
So are you suggesting that Ponie be written in Perl 6 or Perl 5?
If you
Ponie is being written in C. As it stands, it's a refactoring of the
current perl code base to
use Parrot internals. When all the intended changes have finished,
it will still have a C core that compiles Perl code to Parrot bytecode.
want to remain consistent with the self hosting approach and maximize
the Perl 5 userbase, the Ponie compiler Perl should be written in Perl
5, and thus self hosted as well via itself on Parrot. If this were
the
case, work on bootstrapping Ponie in Perl 5 could begin now.
While it would be an interesting exercise to bootstrap Perl 5 in Perl
5, it is by no means the
simplest way of making things work. The stated goal for Ponie is to
ensure an easy transition
from Perl 5 to the Parrot (and Perl 6) world. If you were simply to
throw out the existing
implementation, there's a good chance that you'd mess up bindings to
XS and other
evil assumptions that CPAN core module writers made.
Oh, and work has already begun on Ponie, as can be seen in the
archived posts on http://www.nntp.perl.org/group/perl.ponie.dev/
Norman
