[Python-Dev] Py_DECREF causes spurious gcc warning
Zack Weinberg
zack at codesourcery.com
Wed Dec 17 19:36:21 EST 2003
"Tim Peters" <tim.one at comcast.net> writes:
> This is what leads to the bletcherous
>
> do {
> the real macro guts go here
> } while(0)
>
> form of macro definition. Py_DECREF could be rewritten in that form -- but
> I've puked enough for one day <splat>.
Should, not just could. Yeah, it's bletcherous, but it's the only
way to be sure. (Short of inline functions.)
zw
More information about the Python-Dev
mailing list