+++ /dev/null
-\r
-/* Float object interface */\r
-\r
-/*\r
-PyFloatObject represents a (double precision) floating point number.\r
-*/\r
-\r
-#ifndef Py_FLOATOBJECT_H\r
-#define Py_FLOATOBJECT_H\r
-#ifdef __cplusplus\r
-extern "C" {\r
-#endif\r
-\r
-typedef struct {\r
- PyObject_HEAD\r
- double ob_fval;\r
-} PyFloatObject;\r
-\r
-PyAPI_DATA(PyTypeObject) PyFloat_Type;\r
-\r
-#define PyFloat_Check(op) PyObject_TypeCheck(op, &PyFloat_Type)\r
-#define PyFloat_CheckExact(op) (Py_TYPE(op) == &PyFloat_Type)\r
-\r
-/* The str() precision PyFloat_STR_PRECISION is chosen so that in most cases,\r
- the rounding noise created by various operations is suppressed, while\r
- giving plenty of precision for practical use. */\r
-\r
-#define PyFloat_STR_PRECISION 12\r
-\r
-#ifdef Py_NAN\r
-#define Py_RETURN_NAN return PyFloat_FromDouble(Py_NAN)\r
-#endif\r
-\r
-#define Py_RETURN_INF(sign) do \\r
- if (copysign(1., sign) == 1.) { \\r
- return PyFloat_FromDouble(Py_HUGE_VAL); \\r
- } else { \\r
- return PyFloat_FromDouble(-Py_HUGE_VAL); \\r
- } while(0)\r
-\r
-PyAPI_FUNC(double) PyFloat_GetMax(void);\r
-PyAPI_FUNC(double) PyFloat_GetMin(void);\r
-PyAPI_FUNC(PyObject *) PyFloat_GetInfo(void);\r
-\r
-/* Return Python float from string PyObject. Second argument ignored on\r
- input, and, if non-NULL, NULL is stored into *junk (this tried to serve a\r
- purpose once but can't be made to work as intended). */\r
-PyAPI_FUNC(PyObject *) PyFloat_FromString(PyObject*, char** junk);\r
-\r
-/* Return Python float from C double. */\r
-PyAPI_FUNC(PyObject *) PyFloat_FromDouble(double);\r
-\r
-/* Extract C double from Python float. The macro version trades safety for\r
- speed. */\r
-PyAPI_FUNC(double) PyFloat_AsDouble(PyObject *);\r
-#define PyFloat_AS_DOUBLE(op) (((PyFloatObject *)(op))->ob_fval)\r
-\r
-/* Write repr(v) into the char buffer argument, followed by null byte. The\r
- buffer must be "big enough"; >= 100 is very safe.\r
- PyFloat_AsReprString(buf, x) strives to print enough digits so that\r
- PyFloat_FromString(buf) then reproduces x exactly. */\r
-PyAPI_FUNC(void) PyFloat_AsReprString(char*, PyFloatObject *v);\r
-\r
-/* Write str(v) into the char buffer argument, followed by null byte. The\r
- buffer must be "big enough"; >= 100 is very safe. Note that it's\r
- unusual to be able to get back the float you started with from\r
- PyFloat_AsString's result -- use PyFloat_AsReprString() if you want to\r
- preserve precision across conversions. */\r
-PyAPI_FUNC(void) PyFloat_AsString(char*, PyFloatObject *v);\r
-\r
-/* _PyFloat_{Pack,Unpack}{4,8}\r
- *\r
- * The struct and pickle (at least) modules need an efficient platform-\r
- * independent way to store floating-point values as byte strings.\r
- * The Pack routines produce a string from a C double, and the Unpack\r
- * routines produce a C double from such a string. The suffix (4 or 8)\r
- * specifies the number of bytes in the string.\r
- *\r
- * On platforms that appear to use (see _PyFloat_Init()) IEEE-754 formats\r
- * these functions work by copying bits. On other platforms, the formats the\r
- * 4- byte format is identical to the IEEE-754 single precision format, and\r
- * the 8-byte format to the IEEE-754 double precision format, although the\r
- * packing of INFs and NaNs (if such things exist on the platform) isn't\r
- * handled correctly, and attempting to unpack a string containing an IEEE\r
- * INF or NaN will raise an exception.\r
- *\r
- * On non-IEEE platforms with more precision, or larger dynamic range, than\r
- * 754 supports, not all values can be packed; on non-IEEE platforms with less\r
- * precision, or smaller dynamic range, not all values can be unpacked. What\r
- * happens in such cases is partly accidental (alas).\r
- */\r
-\r
-/* The pack routines write 4 or 8 bytes, starting at p. le is a bool\r
- * argument, true if you want the string in little-endian format (exponent\r
- * last, at p+3 or p+7), false if you want big-endian format (exponent\r
- * first, at p).\r
- * Return value: 0 if all is OK, -1 if error (and an exception is\r
- * set, most likely OverflowError).\r
- * There are two problems on non-IEEE platforms:\r
- * 1): What this does is undefined if x is a NaN or infinity.\r
- * 2): -0.0 and +0.0 produce the same string.\r
- */\r
-PyAPI_FUNC(int) _PyFloat_Pack4(double x, unsigned char *p, int le);\r
-PyAPI_FUNC(int) _PyFloat_Pack8(double x, unsigned char *p, int le);\r
-\r
-/* Used to get the important decimal digits of a double */\r
-PyAPI_FUNC(int) _PyFloat_Digits(char *buf, double v, int *signum);\r
-PyAPI_FUNC(void) _PyFloat_DigitsInit(void);\r
-\r
-/* The unpack routines read 4 or 8 bytes, starting at p. le is a bool\r
- * argument, true if the string is in little-endian format (exponent\r
- * last, at p+3 or p+7), false if big-endian (exponent first, at p).\r
- * Return value: The unpacked double. On error, this is -1.0 and\r
- * PyErr_Occurred() is true (and an exception is set, most likely\r
- * OverflowError). Note that on a non-IEEE platform this will refuse\r
- * to unpack a string that represents a NaN or infinity.\r
- */\r
-PyAPI_FUNC(double) _PyFloat_Unpack4(const unsigned char *p, int le);\r
-PyAPI_FUNC(double) _PyFloat_Unpack8(const unsigned char *p, int le);\r
-\r
-/* free list api */\r
-PyAPI_FUNC(int) PyFloat_ClearFreeList(void);\r
-\r
-/* Format the object based on the format_spec, as defined in PEP 3101\r
- (Advanced String Formatting). */\r
-PyAPI_FUNC(PyObject *) _PyFloat_FormatAdvanced(PyObject *obj,\r
- char *format_spec,\r
- Py_ssize_t format_spec_len);\r
-\r
-/* Round a C double x to the closest multiple of 10**-ndigits. Returns a\r
- Python float on success, or NULL (with an appropriate exception set) on\r
- failure. Used in builtin_round in bltinmodule.c. */\r
-PyAPI_FUNC(PyObject *) _Py_double_round(double x, int ndigits);\r
-\r
-\r
-\r
-#ifdef __cplusplus\r
-}\r
-#endif\r
-#endif /* !Py_FLOATOBJECT_H */\r
projects / mirror_edk2.git / blobdiff