diff options
| author | Tim Peters <tim.peters@gmail.com> | 2004-07-22 01:46:43 +0000 |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2004-07-22 01:46:43 +0000 |
| commit | 9c23abff33b146cb173bf3a27b1cbeefef4a5c66 (patch) | |
| tree | ff4cbe0cb93839ae67f7f4a1043257470f690945 /Include/object.h | |
| parent | 3a56a43e2aae17c3e80651df97a2839392520dee (diff) | |
| download | cpython-9c23abff33b146cb173bf3a27b1cbeefef4a5c66.tar.gz | |
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.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/object.h b/Include/object.h index 60cf1464fa..5db4dac061 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 |