I heard that Parrot has a JIT compiler. If I understand this correctly,
does this mean Parrot bytecode is converted to native machine hardware
code before execution? If so, it is a good idea.
JIT is great, however, will it still be possible to run the Parrot
bytecode on the interpretor?
Also,
Nicholas Clark wrote:
On 9 Mar 2005, at 23:34, Millsa Erlas wrote:
Also, what is the status of Ponie and providing complete
interoperability between Perl 5 language and documented XS support and
Parrot and Perl 6? I believe that assuring
For various internal and external reasons work has been
Autrijus Tang wrote:
After a IRC meeting with Leo, I've outlined my roadmap of how to make the three
compiler backends in Pugs to work in concert to provide a much faster evaluator:
http://use.perl.org/~autrijus/journal/23890
Note that existing code in the Eval monad need not be rewritten; also
Markus Laire wrote:
I've been following the development of pugs (http://pugscode.org/), so I
can give a short answer based on that.
While pugs is currently written in Haskell, roadmap does mention the
idea to eventually port pugs to perl6 if needed, which would give us a
Perl 6 compiler writte
What is the current status of the development of the Parrot and the Perl
6 compiler written in Perl? I hope that producing a Perl 6 compiler
written in Perl 6 and the Parrot VM is still a high priority and is
being actively developed as the premier compiler and VM for the Perl 6
language. A Per
