News for hackers. Stuff that matters.

A comment on Pycket: A Tracing JIT for a Functional Language.

Re:Pycket: A Tracing JIT for a Functional Language by 616c on Friday May 15, 2015 @04:28AM (#9549485)
I had trouble compiling Pixie a few weeks ago specifically because it tries to embed PyPy from source, IIRC, and I cold not figure out how to tell it to talk to the PyPy I had already compiled. Looks like I need to try again.

And if this comes to Racket, this formidable stack will be unstoppabe!

[ Parent | on HN ]
Re:Pycket: A Tracing JIT for a Functional Language by andrewchambers on Friday May 15, 2015 @04:43AM (#9549530)
You have totally misunderstood what pypy and rpython are. Pixie is using the pypy toolchain to build a binary, the rpython toolchain to be precise.

This is not the same as the pypy binary you have installed.

[ Parent | on HN ]
Re:Pycket: A Tracing JIT for a Functional Language by 616c on Friday May 15, 2015 @05:09AM (#9549583)
Well thanks for clarifying. But my point is: cannot I use the already configured pypy toolchain I used to build pypy from source on my machine anyway?

https://aur.archlinux.org/packages/?O=0&K=pypy

In any event, I will invest more time into this. All the talk of RPython, and (yes I know they are unrelated) Cython toolkits makes Python look wonderful again.

[ Parent | on HN ]