> Paul wrote >> Robert wrote: >>> Paul Schlie wrote: >>> - agreed, and thereby objects having no legitimate trap representation, >>> such as most if not all implementations of integers and floating point >>> objects on most if not all current target machines, and thereby their >>> access does not invoke an undefined behavior. >> >> First of all, trap representations of COURSE exist for floating-point >> objects, I guess you don't know fpt formats (most people don't). > > - 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.
- admittedly, SNaN values may be considered as such; however ints would appear to have no counterpart.