Author: Armin Rigo <[email protected]>
Branch:
Changeset: r2136:4debac35be68
Date: 2015-05-30 14:53 +0200
http://bitbucket.org/cffi/cffi/changeset/4debac35be68/
Log: Precision
diff --git a/doc/source/cdef.rst b/doc/source/cdef.rst
--- a/doc/source/cdef.rst
+++ b/doc/source/cdef.rst
@@ -380,7 +380,8 @@
not work with ``verify()``.) The ``int...`` can be replaced with
``long...`` or ``unsigned long long...`` or any other primitive
integer type, with no effect. The type will always map to one of
- ``(u)int(8,16,32,64)_t``.
+ ``(u)int(8,16,32,64)_t`` in Python, but in the generated C code,
+ only ``foo_t`` is used.
* unknown types: the syntax "``typedef ... foo_t;``" declares the type
``foo_t`` as opaque. Useful mainly for when the API takes and returns
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
