Hi Armin, At a minimum tighter execution is required as well as sharing memory. But on the other hand you have raised the bar so high with cffi, having a clean and unbloated interface, that it would be nice if a library with a similar spirit existed for java. Having support in PyPy's JIT to remove all the marshalling types would be a big plus on top of the shared memory as well as some integration between the 2 GCs would likely be required. Maybe the best approach would be a combination of existing libraries and a new interface that allows for sharing of memory. Maybe similar to numpy arrays with a better API that avoids the pit falls of numpy relying on CPython semantics/implementation details. After all the only thing that needs to be eliminated is the copying/serialization of large data arrays/structures. John On Thu, Mar 24, 2016 at 12:20 PM, Armin Rigo <arigo@tunes.org> wrote:
Hi John,
On 24 March 2016 at 13:22, John Camara <john.m.camara@gmail.com> wrote:
(...) Thus the need for a jffi library.
When I hear "a jffi library" I'm thinking about a new library with a new API. I think what you would really like instead is to keep the existing libraries, but adapt them internally to allow tighter execution of the Python and Java VMs.
I may be completely wrong about that, but you're also talking to the wrong guys in the first place :-)
A bientôt,
Armin.