Whats the problem with cppyy?
Why don't extend it rather than build new solution based on pycparser?
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
I think that what laura meant was that pypy people should talk to
luajit people, because if someone came to talk to pypy about ctypes
(the other big ffi for a dynamic language) pypy devs would have said
"don't copy us because in pratictice this design is bad.". As you said
that you talked to luajit
Hi,
On Tue, May 29, 2012 at 10:15 AM, Antonio Cuni wrote:
>> A wild guess: Sleep is a WINAPI function, with a calling convention
>> different than
>> the default C convention. Maybe this makes a difference with the ffi module?
Yes, exactly. I don't see anything related to that in module/_ffi
t
On 05/29/2012 12:05 AM, Amaury Forgeot d'Arc wrote:
> A wild guess: Sleep is a WINAPI function, with a calling convention different
> than
> the default C convention. Maybe this makes a difference with the ffi module?
I bet that the problem is inside the implementation of CALL_RELEASE_GIL in the
