Source

cffi / README.md

Diff from to

File README.md

-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
 ----------
 
 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