On Thu, May 24, 2012 at 9:31 AM, Michal Bendowski wrote:
> Just two add my two cents: I made the JVM backend translate the
> standard interpreter in the jvm-improvements branch a few months ago
> (just a few changes). The branch has been closed though and I had a
> busy time so I didn't do anythin
On Thu, May 24, 2012 at 9:19 AM, Timothy Baldridge wrote:
> Side note, I would really love to see the JVM backend more maintained.
> If I could write Clojure in RPython, then run it on the JVM...with a
> full tracing JIT, that would just be insanely awesome.
Holy turtles all the way down batman!
On Thu, May 24, 2012 at 7:24 AM, wrote:
> if it can find the errors, then the fastest is to use:
>
> pypy/bin/checkmodule.py
>
> but I very rarely find errors that way. Second is to write a jit test,
> which does partial translation (only of the code reachable from the test)
> and can use a f
On Thu, Jan 12, 2012 at 3:06 PM, Alex Gaynor wrote:
> I'm mostly an observerer on the JVM + PyPy front, but my understanding is
> JPype or the like would be to solve the issue of "how do we test this
> without compiling all of PyPy".
Ah I see - a very different point of integration. Thanks for the
2012/1/12 Michał Bendowski :
> Hello everyone,
>
> Back in the summer I asked on this mailing list if there's interest in moving
> the JVM backend forward. Back then there was some enthusiasm, so I got back
> to it when I had the chance, which unfortunately was a few months later. The
> suggesti
