Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
- From: Jeff☠Relf <Jeff_Relf@xxxxxxxxx>
- Date: 26 Jul 2007 14:45:18 GMT
Back around 1995, VC's default settings had
a floating-point divide-by-zero would terminate the app.
Even today, an integer divide-by-zero terminates the app.
Why stop the whole show just because an int overflowed ?
How can I turn this " feature " off ?
Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
F.Y.I.: For for the 8 bit exponent in VC's “ float ”,
infinity is 255 ( 2^128, “ _isnan() == 1 ” )
and zero is zero ( notionally 2^-127, provided: “ _clearfp() == 0 ” ).
The largest " true " float is 2^128 - 1 ( FLT_MAX )
and the smallest is 2^-126 ( FLT_MIN ).
.
- Follow-Ups:
- Re: Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
- From: Tim Roberts
- Re: Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
- From: Carl Daniel [VC++ MVP]
- Re: Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
- Prev by Date: How to disable Windows FIle Protection System.
- Next by Date: Re: Get Visual Studio to compile a different C file from the one in the project..?
- Previous by thread: How to disable Windows FIle Protection System.
- Next by thread: Re: Why doesn't an underflow ( e.g. X *= 0 ) bring down the house ?
- Index(es):
Relevant Pages
|
