mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-01 18:51:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 21

Stop trying to cater to platforms with a broken HUGE_VAL definition. It

Browse source 
breaks other platforms (in this case, the hack for broken Cray systems in
turn caused failure on a Mac system broken in a different way).
This commit is contained in:
Tim Peters 2002-07-03 03:31:20 +00:00
parent 60ae701b3a
commit 1de41bfbc0
2 changed files with 25 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

19
Include/pyport.h
View file

@ -229,19 +229,14 @@ extern "C" {
*/
#define Py_IS_INFINITY(X) ((X) && (X)*0.5 == (X))
/* According to
* http://www.cray.com/swpubs/manuals/SN-2194_2.0/html-SN-2194_2.0/x3138.htm
* on some Cray systems HUGE_VAL is incorrectly (according to the C std)
* defined to be the largest positive finite rather than infinity. We need
* the std-conforming infinity meaning (provided the platform has one!).
*
* Then, according to a bug report on SourceForge, defining Py_HUGE_VAL as
* INFINITY caused internal compiler errors under BeOS using some version
* of gcc. Explicitly casting INFINITY to double made that problem go away.
/* HUGE_VAL is supposed to expand to a positive double infinity. Python
* uses Py_HUGE_VAL instead because some platforms are broken in this
* respect. We used to embed code in pyport.h to try to worm around that,
* but different platforms are broken in conflicting ways. If you're on
* a platform where HUGE_VAL is defined incorrectly, fiddle your Python
* config to #define Py_HUGE_VAL to something that works on your platform.
*/
#ifdef INFINITY
#define Py_HUGE_VAL ((double)INFINITY)
#else
#ifndef Py_HUGE_VAL
#define Py_HUGE_VAL HUGE_VAL
#endif