On Sat, Jul 14, 2012 at 4:56 AM, Lucian Branescu <[email protected]> wrote: > On 14 July 2012 01:21, Jonathan "Duke" Leto <[email protected]> wrote: >> For better (or worse) Parrot is mentioned here: >> >> http://morepypy.blogspot.de/2012/07/hello-everyone.html >> >> It is not clear which "inherited problems" they are talking about. > > I think fijal refers to the effort of mapping the semantics of an > existing language (say, Python) on top of the facilities offered by an > existing VM (say, JVM), which come with their existing assumptions and > semantics.
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. -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/ _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
