This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author arigo
Recipients Arfrever, Tom Krauss, amaury.forgeotdarc, arigo, mark.dickinson, meador.inge, rutsky
Date 2017-01-29.22:23:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
* Tom: the issue is unrelated to cffi, but both ctypes and cffi could proceed to support C complexes, now that libffi support has been added.

* Mark: the problem is that the text you quote from the C standard fixes the representation of a complex in memory, but doesn't say anything about directly passing a complex as argument or return value to a function call.  Platforms use custom ways to do that.  The text you quote says a complex is an array of two real numbers; but passing an array as argument to a function works by passing a pointer to the first element.  Typically, this is not how complexes are passed: instead, some pointerless form of "passing two real numbers" is used.
Date User Action Args
2017-01-29 22:23:09arigosetrecipients: + arigo, amaury.forgeotdarc, mark.dickinson, Arfrever, meador.inge, rutsky, Tom Krauss
2017-01-29 22:23:09arigosetmessageid: <>
2017-01-29 22:23:09arigolinkissue16899 messages
2017-01-29 22:23:09arigocreate