Antoine Pitrou added the comment: > >> I think the feature is somewhat desirable; I agree code combining > >> different types in MIN or MAX is flawed - if it is intentional, asking > >> for an explicit cast is not asking too much. > > > > I don't agree. Trying to battle with C's semantics doesn't seem very > > productive, especially if it's only done in a single pair of macros. > > What do you disagree with? That "combining different types in MIN and MAX > is flawed"? Or that "asking for an explicit cast is not asking too much"?
The former. If C allows it then what's the point of special-casing Py_MIN and Py_MAX to disallow it? It will only catch a very small fraction of cases anyway. Again, if this is a serious issue (which I don't think it is), it would be better handled by choosing the appropriate compiler options. ---------- _______________________________________ 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
