Message 79088 - Python tracker

➜

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	mark.dickinson
Recipients	christian.heimes, mark.dickinson, rpetrov, skip.montanaro
Date	2009-01-04.22:27:00
SpamBayes Score	0.18615173
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
Looking at this again, I don't like my solution. I think it would be better to fix Py_IS_INFINITY directly, putting all the complication into one place; then users of Py_IS_INFINITY don't have to spend time worrying about whether they should be calling Py_FORCE_DOUBLE or not. The fixed Py_IS_INFINITY will likely be slower, but this only matters on platforms that don't provide isinf, isnan; it seems that Solaris is the only such platform in common use.

Looking at this again, I don't like my solution.

I think it would be better to fix Py_IS_INFINITY directly, putting all the 
complication into one place;  then users of Py_IS_INFINITY don't have to 
spend time worrying about whether they should be calling Py_FORCE_DOUBLE 
or not.

The fixed Py_IS_INFINITY will likely be slower, but this only matters on 
platforms that don't provide isinf, isnan;  it seems that Solaris is the 
only such platform in common use.

History
Date	User	Action	Args
2009-01-04 22:27:01	mark.dickinson	set	recipients: + mark.dickinson, skip.montanaro, christian.heimes, rpetrov
2009-01-04 22:27:01	mark.dickinson	set	messageid: <[email protected]>
2009-01-04 22:27:00	mark.dickinson	link	issue4575 messages
2009-01-04 22:27:00	mark.dickinson	create