diff options
author | Armin Rigo <arigo@tunes.org> | 2013-02-16 10:17:34 +0100 |
---|---|---|
committer | Armin Rigo <arigo@tunes.org> | 2013-02-16 10:17:34 +0100 |
commit | ee1639c733209b7b6830cd2b00f1264c648fb8b8 (patch) | |
tree | d800d6a84de4f3f76a719d3daa94c5d2d45ca3d1 /doc | |
parent | 7ec8bd2d5beb8d083bb81a0c9f1752fb1b3204b4 (diff) | |
download | cffi-ee1639c733209b7b6830cd2b00f1264c648fb8b8.tar.gz |
Moving the determination of the base integer type of an enum
out of C code, into the 'cffi' package. This is work in progress;
it should eventually permit the new test to fully pass. For now
wrote a warning in the doc.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/source/index.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/source/index.rst b/doc/source/index.rst index 3c23b33..813ce22 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -1216,7 +1216,10 @@ Known missing features that are GCC or MSVC extensions: Enum types follow the GCC rules: they are defined as the first of ``unsigned int``, ``int``, ``unsigned long`` or ``long`` that fits all numeric values. Note that the first choice is unsigned. In CFFI - 0.5 and before, it was always ``int``. + 0.5 and before, it was always ``int``. *Unimplemented: if the very + large values are not declared, the enum size will be incorrectly + deduced! Work around this by making sure that you name the largest + value and/or any negative value in the cdef.* Debugging dlopen'ed C libraries |