Thank you for your reply.
Ive thought about it and it is really perfectly fine
with me if large parts (or all) of the old perl
interpreter where bundled with Parrot in order to
provide Perl5 compatability on Parrot. If using
existing Perl5 interpretor code saves effort and works
well, but still al
Milscvaer writes:
> Running the old Perl5 interpretor and the Parrot in the same process
> is not a great solution, since this would mean that there would be two
> completely seperate interpretor codebases to support. A big part of
> Parrot is to allow several languages to use the same interpretor,
Matthew Walton <[EMAIL PROTECTED]> wrote:
> I suggest you read more about Parrot... it's designed to allow these
> things. There is a project (Ponie) to make Perl 5 run on Parrot, and
> there will be other languages as well - which will be able to call each
> others libraries. Making the Perl 5 lib
I suggest you read more about Parrot... it's designed to allow these
things. There is a project (Ponie) to make Perl 5 run on Parrot, and
there will be other languages as well - which will be able to call each
others libraries. Making the Perl 5 libraries available to Perl 6 being
a primary mot
