Inheritance diagram for std::numeric_limits_base:
Static Public Attributes | |
const bool | is_specialized |
const int | digits |
const int | digits10 |
const bool | is_signed |
const bool | is_integer |
const bool | is_exact |
const int | radix |
const int | min_exponent |
const int | min_exponent10 |
const int | max_exponent |
const int | max_exponent10 |
const bool | has_infinity |
const bool | has_quietNaN |
const bool | has_signalingNaN |
const float_denorm_style | has_denorm |
const bool | has_denorm_loss |
const bool | is_iec559 |
const bool | is_bounded |
const bool | is_modulo |
const bool | traps |
const bool | tinyness_before |
const float_round_style | round_style |
The static
const
members are usable as integral constant expressions.
Definition at line 192 of file limits.
|
The number of |
|
The number of base 10 digits that can be represented without change. Definition at line 43 of file limits.cc. |
|
See std::float_denorm_style for more information. Definition at line 55 of file limits.cc. |
|
"True if loss of accuracy is detected as a denormalization loss, rather than as an inexact result." [18.2.1.2]/42 Definition at line 56 of file limits.cc. |
|
True if the type has a representation for positive infinity. Definition at line 52 of file limits.cc. |
|
True if the type has a representation for a quiet (non-signaling) "Not a Number." Definition at line 53 of file limits.cc. |
|
True if the type has a representation for a signaling "Not a Number." Definition at line 54 of file limits.cc. |
|
"True if the set of values representable by the type is finite. All built-in types are bounded, this member would be false for arbitrary precision types." [18.2.1.2]/54 Definition at line 58 of file limits.cc. |
|
True if the type uses an exact representation. "All integer types are exact, but not all exact types are integer. For example, rational and fixed-exponent representations are exact but not integer." [18.2.1.2]/15 Definition at line 46 of file limits.cc. |
|
True if-and-only-if the type adheres to the IEC 559 standard, also known as IEEE 754. (Only makes sense for floating point types.) Definition at line 57 of file limits.cc. |
|
True if the type is integer. Definition at line 45 of file limits.cc. |
|
True if the type is modulo, that is, if it is possible to add two positive numbers and have a result that wraps around to a third number that is less. Typically false for floating types, true for unsigned integers, and true for signed integers. Definition at line 59 of file limits.cc. |
|
True if the type is signed. Definition at line 44 of file limits.cc. |
|
This will be true for all fundamental types (which have specializations), and false for everything else. Definition at line 41 of file limits.cc. |
|
The maximum positive integer such that |
|
The maximum positive integer such that 10 raised to that power is in the range of representable finite floating point numbers. Definition at line 51 of file limits.cc. |
|
The minimum negative integer such that |
|
The minimum negative integer such that 10 raised to that power is in the range of normalized floating point numbers. Definition at line 49 of file limits.cc. |
|
For integer types, specifies the base of the representation. For floating types, specifies the base of the exponent representation. Definition at line 47 of file limits.cc. |
|
See std::float_round_style for more information. This is only meaningful for floating types; integer types will all be round_toward_zero. Definition at line 62 of file limits.cc. |
|
True if tinyness is detected before rounding. (see IEC 559) Definition at line 61 of file limits.cc. |
|
True if trapping is implemented for this type. Definition at line 60 of file limits.cc. |