Where does C++ standard define the value range of float types?
https://stackoverflow.com/questions/1816552
-
08-07-2019 - |
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
As far as I know floating point values are of the form n * 2^e, with
- float range being n = -(2^23-1) - (2^23-1), and e = -126 - 127,
- double range being n = -(2^52-1) - (2^52-1), and e = -1022 - 1023
I was looking through the C++ standard, but failed to find the place where the standard specifies this, or mandates the association of the float, double and long double types with ranges defined in other (IEEE) standards. The only related thing I found in 3.9.1.8 is:
There are three floating point types: float, double, and long double. The type double provides at least as much precision as float, and the type long double provides at least as much precision as double. The set of values of the type float is a subset of the set of values of the type double; the set of values of the type double is a subset of the set of values of the type long double. The value representation of floating-point types is implementation-defined.
And no mention of the minimum range provided by the type.
Where/how does the standard specify the (minimum?) value range of the floating point types? Or can a compiler freely choose any value range and still be standard compliant?
Solution
Just like integer numberic limits, the limits for float, double and long double are imported from the C standard. The minimum value for constants FLT_MAX, DBL_MAX and LDBL_MAX is 1E+37. For their *_MIN variants the maximum value is 1E-37.
OTHER TIPS
What you've quoted is all that's guaranteed about the floating point types in C++. As it says, their representation is implementation-defined.
You can, though, query for information about the limits and whether the types are IEC 559 (IEEE 754) specified types using the std::numeric_limits templates in <limits>.
The standard doesn't specify such things because they are often hardware dependent and change over time. While today 32 bits are considered a standard, in 10 years doing things in less than 64 bit may possibly seem distasteful.
