commit | 5980ff2d924b55cf963e9fb69f41c86b45f4099a | [log] [tgz] |
---|---|---|
author | Tim Peters <tim.peters@gmail.com> | Thu Jul 22 01:46:43 2004 +0000 |
committer | Tim Peters <tim.peters@gmail.com> | Thu Jul 22 01:46:43 2004 +0000 |
tree | 010601edc1df19e1b5dc178850ca632d12a2f998 | |
parent | aa1c7ff7e8dd9dbda8ed935b7db7c9a81a164621 [diff] |
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!).