This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients loewis, pitrou, vstinner
Date 2012-08-03.22:23:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344032470.3377.27.camel@localhost.localdomain>
In-reply-to <20120804001819.Horde.3MMmdqGZi1VQHE4rqsTXyVA@webmail.df.eu>
Content
> >> 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.
History
Date User Action Args
2012-08-03 22:23:44pitrousetrecipients: + pitrou, loewis, vstinner
2012-08-03 22:23:42pitroulinkissue15530 messages
2012-08-03 22:23:42pitroucreate