Rationale for a VM + compiler approach instead of an interpreter?

Hello, I have been reading up (a bit) on Perl6 and found most articles mentioning Parrot + Rakudo as the primary tools for development using the language. Is there any rationale for going with the above approach instead of an interpreter based one? Also, would there be community

Re: Rationale for a VM + compiler approach instead of an interpreter?

Hi, On 06.12.2014 18:55, Mayuresh Kathe wrote: Hello, I have been reading up (a bit) on Perl6 and found most articles mentioning Parrot + Rakudo as the primary tools for development using the language. Well, these days we have three backends (MoarVM, JVM and Rakudo). Is there any rationale

Definitions: compiler vs interpreter [was: Rationale for a VM + compiler approach instead of an interpreter?]

* Moritz Lenz mor...@faui2k3.org [2014-12-06 20:05]: First of all, the lines between interpreters and compilers a bit blurry. People think of Perl 5 as an interpreter, but actually it compilers to bytecode, which is then run by a runloop. So it has a compiler and an interpreter stage. This is

Re: Rationale for a VM + compiler approach instead of an interpreter?

On 2014-12-07 00:31, Moritz Lenz wrote: Hi, On 06.12.2014 18:55, Mayuresh Kathe wrote: Hello, I have been reading up (a bit) on Perl6 and found most articles mentioning Parrot + Rakudo as the primary tools for development using the language. Well, these days we have three backends (MoarVM,