Antoine Pitrou added the comment: > > People should simply avoid doing this kind of thing, as it's > > knowingly fragile, and trivial to avoid anyway. > Is this documented in the C API guide, or somewhere else?
I don't think so, but it's common C wisdom that you shouldn't pass arguments which have side effects to a macro, except if you are sure the macro allows it. > In any case, notifying people so they can quickly check their code > seems much nicer than having them figure this out the hard way. I see it as a double-edged sword: if we start adding a warning for this macro, people will expect us to do it for every other macro, which we aren't doing right now. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16602> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
