Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.1 on 2022-01-26 at 16:00 UTC+1 (a few minutes of down time)

Commit ce68c861 authored by Armin Rigo's avatar Armin Rigo
Browse files

Reformat and mention the mailing list.

parent cf451d1b82e4
ffi
===
cffi
====
Foreign Function Interface for Python.
Foreign Function Interface for Python calling C code.
Mailing list: https://groups.google.com/forum/#!forum/python-cffi
Initial motivation
......@@ -21,17 +23,27 @@ Next steps
----------
the verify() step, which should handle:
* completing "...;" structs
* checking the other structs, and the arguments to functions, using the real C compiler
* simple "#define FOO value" macros
* macros of the kind "#define funcname otherfuncname"
* more complicated macros "#define foo(a, b, c) ..."
* checking and correcting the value of the enum {} declarations
* probably also fixing the array lengths, e.g. declared as a field "int foo[...];"
* completing "...;" structs
* checking the other structs, and the arguments to functions, using the real C compiler
* simple "#define FOO value" macros
* macros of the kind "#define funcname otherfuncname"
* more complicated macros "#define foo(a, b, c) ..."
* checking and correcting the value of the enum {} declarations
* probably also fixing the array lengths, e.g. declared as a field "int foo[...];"
generating C extensions:
* this is needed anyway to call macros
* faster, libffi-free way to call C code
* partial blockers: callbacks (probably still use libffi)
* this is needed anyway to call macros
* faster, libffi-free way to call C code
* partial blockers: callbacks (probably still use libffi)
_ffi backend for PyPy
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment