Paul Schlie wrote:
- as trap representation within the context of C is a value representation which is not defined to be a member of a type, where if accessed or produced evokes undefined behavior; so admit as to the best of my knowledge all potentially enclosable values for IEEE floats and doubles are defined, it would seem trap representations don't exist in typical fp implementations, as such an implementation would require more bits of encoding than the type itself requires.
You don't think a signalling NaN is a trap value? The existence of such values (which do indeed cause a trap if loaded), is one of the inspirations for the C language and design in this respect.
