On Wed, Feb 27, 2013 at 1:45 PM, Richard Oudkerk <shibt...@gmail.com> wrote: > On 27/02/2013 9:21am, Maciej Fijalkowski wrote: >>> >>> >That's somehting that will have to be resolved before cffi can be >>> > included in the stdlib, fat binaries are supported by CPython and are used >>> > the binary installers. >>> > >>> >Ronald >> >> if cpython supports it and you can load it using dlopen, it does work >> then (it really is just building a C extension on the API level). > > > On Windows ctypes has CDLL for libraries using the cdecl calling convention > and WINDLL for libraries with the stdcall calling convention. > > I can't see any similar distinction in cffi's documentation. Can cffi > magically work out which calling convention to use, or are you restricted to > the cdecl calling convention?
copy pasting from docs: Windows: you can’t yet specify the calling convention of callbacks. (For regular calls, the correct calling convention should be automatically inferred by the C backend.) Use an indirection, like in the example just above. I think it means you can't use the ABI version and specify the calling convention. It's a reasonable bug report (the calling convention on API version works though) > > -- > Richard > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/fijall%40gmail.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
