Martin v. Löwis added the comment: > I am indifferent with respect to the use of the GCC extensions, but > getting rid of the umpteen different implementations of MIN/MAX is a > nice , albeit very minor, cleanup.
I think that's a different issue from the one we have here, though (which specifically targets using GCC extensions). I also agree that combining the MIN/MAX implementation (naturally into Py_MIN/Py_MAX) is desirable - I don't think that needs an issue. I'm opposed to reducing the number of times of expression evaluation on GCC (i.e. statement expressions). If there are cases where the double evaluation has side effects, I'd rather have it fail on GCC as well (and not just on MSVC). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15530> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
