summaryrefslogtreecommitdiffstats
path: root/Include/object.h
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2004-07-22 01:46:43 (GMT)
committerTim Peters <tim.peters@gmail.com>2004-07-22 01:46:43 (GMT)
commit5980ff2d924b55cf963e9fb69f41c86b45f4099a (patch)
tree010601edc1df19e1b5dc178850ca632d12a2f998 /Include/object.h
parentaa1c7ff7e8dd9dbda8ed935b7db7c9a81a164621 (diff)
downloadcpython-5980ff2d924b55cf963e9fb69f41c86b45f4099a.zip
cpython-5980ff2d924b55cf963e9fb69f41c86b45f4099a.tar.gz
cpython-5980ff2d924b55cf963e9fb69f41c86b45f4099a.tar.bz2
SF bug 994255: Py_RETURN_NONE causes too much warnings
Rewrote Py_RETURN_{NONE, TRUE, FALSE} to expand to comma expressions rather than "do {} while(0)" thingies. The OP complained because he likes using MS /W4 sometimes, and then all his uses of these things generate nuisance warnings about testing a constant expression (in the "while(0)" part). Comma expressions don't have this problem (although it's a lucky accident that comma expressions suffice for these macros!).
Diffstat (limited to 'Include/object.h')
-rw-r--r--Include/object.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/object.h b/Include/object.h
index 60cf146..5db4dac 100644
--- a/Include/object.h
+++ b/Include/object.h
@@ -650,7 +650,7 @@ PyAPI_DATA(PyObject) _Py_NoneStruct; /* Don't use this directly */
#define Py_None (&_Py_NoneStruct)
/* Macro for returning Py_None from a function */
-#define Py_RETURN_NONE do {Py_INCREF(Py_None); return Py_None;} while (0)
+#define Py_RETURN_NONE return Py_INCREF(Py_None), Py_None
/*
Py_NotImplemented is a singleton used to signal that an operation is