Tim Peters <tim.pet...@gmail.com> added the comment: Just noting there are ways to trick the macro into reading a thing once. For example, embed something like a
((x = arenas[(POOL)->arenaindex].address) || 1) clause early on & refer to x later (where x is some file-scope new variable). obmalloc is not intended to be thread-safe _period_, but I agree the current behavior in the case described is obnoxious enough that if it's easy to worm around it, fine. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8020> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
