At 11:12 AM +0100 1/2/70, James A Duncan wrote:
>Morning (BST) all,
>
>I've started work on B::Parrot, which is a Perl 5 to Parrot
>translation engine. Its very basic at the moment, but I've got it
>successfully translating things like:
>
>my $perliv = 10;
>my $perlpv = "\n";
>print $perliv;
>print $perlpv;
>
>into working, assemble-able parrot code. Before I go any further on
>this crack-fuelled project is there anything I should be aware of?
>Are others working on this? Have I done far too much crack smoking
>to consider doing something like this now?
I think what you're doing makes perfect sense, and it's a good way to
go. It should allow for all programs that are essentially static by
CHECK time to be run on Parrot. (Yes, this leaves out runtime
requires, do file, and string evals, but that's a reasonably small
fraction of the programs out there.
It's not sufficient as a general-purpose, long term solution, but
it's a dandy one for the short to medium term. By all means, please
continue, and if there are things missing from Parrot that'll make it
easier (well, OK, besides the known "we have no lexicals, globals,
hashes, and arrays" thing :) let me know.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
