On Sunday 19 October 2003 11:40 pm, Brett C. wrote: ... > #define Py_RETURN_FALSE do {Py_INCREF(Py_False); return Py_False;} while (0) > > Isn't {Py_INCREF(Py_None); return Py_None} enough? I thought ending a > curly brace with a semi-colon is harmless (equivalent of a NO-OP). Why Not in C: the extra semicolon is an empty statement. So, for example if(...) { } ; else is a syntax error. > bother with the do/while loop? To let the user put a semicolon after the macro and get correct C code. Alex
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4