summaryrefslogtreecommitdiff
path: root/Modules/fcntlmodule.c
diff options
context:
space:
mode:
authorThomas Wouters <thomas@python.org>2006-03-02 17:58:27 +0000
committerThomas Wouters <thomas@python.org>2006-03-02 17:58:27 +0000
commit857b300b2e1c2b27af84d6090ed4810df00f1b16 (patch)
tree4b5e3ddc4b7b3908f28d483d6de96a8556c0f3a2 /Modules/fcntlmodule.c
parent4954b384e48701da5f32e55ba664eeeff74703ce (diff)
downloadcpython-git-857b300b2e1c2b27af84d6090ed4810df00f1b16.tar.gz
Explain why we use the unsigned int format for a signed int variable.
(Should 'code' be cast to the right pointer type?)
Diffstat (limited to 'Modules/fcntlmodule.c')
-rw-r--r--Modules/fcntlmodule.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/Modules/fcntlmodule.c b/Modules/fcntlmodule.c
index d109e29e7c..a368494c96 100644
--- a/Modules/fcntlmodule.c
+++ b/Modules/fcntlmodule.c
@@ -96,6 +96,10 @@ static PyObject *
fcntl_ioctl(PyObject *self, PyObject *args)
{
int fd;
+ /* In PyArg_ParseTuple below, use the unsigned int 'I' format for
+ the signed int 'code' variable, because Python turns 0x8000000
+ into a large positive number (PyLong, or PyInt on 64-bit
+ platforms,) whereas C expects it to be a negative int */
int code;
int arg;
int ret;