Hi Wim,
On 21 July 2017 at 03:17, wrote:
> _ffi.cdef("""
> void _ZN6SimpleC1Ev(void*);
> void _ZN6SimpleC1Ei(void*, int);
> int _ZN6Simple8get_dataEv(void*);
> void _ZN6Simple8set_dataEi(void*, int);
> """)
Ouch, I suppose :-) Explicit C++ mangling. The alternative would be
to use ffi.s
Hi,
[replying to self]
And yes, it is technically possible to write a bindings generator that only
depends on LLVM during offline bindings generation, not at run-time. But
then you'd just have SWIG (albeit with a standards-compliant parser).
it hit me yesterday that instead of generating some
Armin,
If the newly-named '_cppyy' module is more minimal than '_cffi_backend'
'more minimal' is a hard to define term, but a 'wc -l' shows that
_cffi_backend has 8498 lines of python and _cppyy has 4265. Of course, the
latter uses the former, saving lots of code for it. :)
Further, _cppyy in
Hi,
I'm not sure that PyPy developers are following the python-ideas
mailing list, so here is a copy of my email. I really want your
feedback to know if my idea is stupid and if it's feasible. You have a
much better experience with C API compatibility than me ;-)
LWN already wrote an article on t
Hi Jaymin,
Welcome! This looks like an error that the meta-pypy build scripts produce? So
it might be more productive to talk to them, since we don't know how that works.
Cheers,
Carl Friedrich
On July 20, 2017 6:47:22 AM GMT+02:00, JAYMIN DABHI
wrote:
>Hi All,
>
> I am trying to inte
Hi Wim,
On 18 July 2017 at 23:33, wrote:
> I want to be able to do a straight 'pip install cppyy' and then use it
> w/o further gymnastics (this works today for CPython)
Great, I'm +1 on that as well.
If the newly-named '_cppyy' module is more minimal than
'_cffi_backend' and less likely to ch
