Parrot metion on the PyPy blog
Reini Urban
rurban at x-ray.at
Mon Jul 16 16:45:04 UTC 2012
On Mon, Jul 16, 2012 at 11:33 AM, Lucian Branescu
<lucian.branescu at gmail.com> wrote:
> On 16 July 2012 15:47, Reini Urban <rurban at x-ray.at> wrote:
>> He was referring to be tied to an existing set of VM opcodes to
>> implement many languages, which he considers as disadvantage. Mainly
>> talking about .NET (which had to add Iron-style dynamic reflection
>> later) or the JVM.
>>
>> parrot already has all the functionalityy the JVM or .NET was missing
>> and even more (e.g. dynamic types loadable as plugins) and considers
>> it as advantage to share opcodes and bytecode libraries across
>> different languages.
>
> I think he also refers to the difficulty of writing a single fast JIT
> for several languages. PyPy generates a custom JIT for each interpreter
> written in RPython.
Ah yes, sure. You are right.
PyPy also bitches a lot about python upstream changes, which they have
to re-implement constantly.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
More information about the parrot-dev
mailing list