Stickiness of TYPE_MIN_VALUE/TYPE_MAX_VALUE

[Geert Bosch]

On May 30, 2005, at 16:50, Florian Weimer wrote:

> I'll try to phrase it differently: If you access an object whose bit
> pattern does not represent a value in the range given by
> TYPE_MIN_VALUE .. TYPE_MAX_VALUE of the corresponding type, does this
> result in erroneous execution/undefined behavior?  If not, what is the
> exact behavior WRT to out-of-bounds values?
>

This is correct. Note that this is only valid for objects,
in expressions intermediate values may lay outside the range
of the type.