Perl 5 to Parrot

2002-04-04 Thread James A Duncan
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. B

Re: Perl 5 to Parrot

2002-04-04 Thread Rafael Garcia-Suarez
James A Duncan wrote in perl.perl6.internals : > > 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

Re: [PATCH] Parrot_(re)allocate_buffer

2002-04-04 Thread Michel J Lambert
> The concern is that both functions are still using the same arenas, which > means the original problems still wouldn't be solved, and we'd still have to > do all the workarounds around them. ;-) Yeah, but I can't go ahead changing this stuff, especially if all the code isn't converted over to

Re: [PATCH] Parrot_(re)allocate_buffer

2002-04-04 Thread Bryan C. Warnock
On Thursday 04 April 2002 16:30, Michel J Lambert wrote: > > Yeah, but I can't go ahead changing this stuff, especially if all the code > isn't converted over to using it yet. One working step at a time, says > Refactoring Man. :) Say no more... ;-) > > > IIUC, the mem*alloc routines are for

Re: Perl 5 to Parrot

2002-04-04 Thread Melvin Smith
At 11:12 AM 1/2/1970 +0100, 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;