Okay, thanks. I guess I'll look into either running the PyPy interpreter as a subprocess or using something else. Thanks again!
- Bryan Buck On Wed, 03 Jun 2009 13:34 -0500, "Benjamin Peterson" <[email protected]> wrote: > 2009/6/3 Bryan Buck <[email protected]>: > > Thank you for your reply. A subprocess is a possibility, although > > I'd like to avoid it if I can. Of course I was hoping there was some > > already- available way to do this that I had overlooked, but if > > necessary modifying PyPy isn't totally out of the question. How > > difficult is not easily? I guess I would have to change the > > translator to produce a library instead of an executable, and create > > an API for calling the interpreter from C? It does seem like a > > somewhat involved project, but I'm just trying to gauge the relative > > difficulty vs. the other possibilities I have in mind (all of which > > would also take significant effort). > > Because the translation framework bridges such a large gap in > languages, it would take significant effort to pin down a human-usable > PyPy API at the C level. I don't know what your other options are, but > they are almost certainly easier than creating a C-API for PyPy. :) > > > -- > Regards, Benjamin _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
