1

I have two console apps (msvc 2008). When they have division by zero, they behave differently. My questions are below.

a) In one app, result of division by zero shows as 1.#INF000000000000 as debugger.
Printf "%4.1f" prints it as "1.$".

b) In another app, result of division by zero 9.2559631349317831e+061 in debugger.
Printf "%4.1f" prints it as "-1.$".

  1. Why neither app has exception or signal on div by zero ?
    Isn't exception/signal a default dehavour ?

  2. What are define names for the two constants above ?

  3. Generally, If I check for denominator == 0 before div, then which define value shall I use for dummy result ? DBL_MIN ok ? I found that NaN value is not.

  4. Can I tell stdio how to format one specific double value as char string I tell it? I realize it's too much to ask. But it would be nice to tell stdio to print, say, "n/a" for vaues DBL_MIN in my app, as example.

  5. How shall I approach, for best portability, division-by-zero and printing it's results ? By printing, I mean "print number as 'n/a' if it's a result of division by zero".
    What is not clear here to me, how shall I represent result of div-by-zero in one double, in a portable way.

  6. Why two different results? It is compiler options ?

Compiler is C++, but used very much like C. Thanks.

Andrei
  • 8,606
  • 10
  • 35
  • 43
  • 1
    Because division by zero is not a specified standard exception. See this post http://stackoverflow.com/questions/4747934/c-catch-a-divide-by-zero-error for more info. – Mahesh Mar 22 '11 at 23:01
  • @Mahesh: That questions handles *integer* division-by-zero. This question is about floating-point operations, which are handled much differently. – Lindydancer Apr 09 '11 at 10:35

1 Answers1

1

When doing floating-point division by zero, the result should be infinity (represented with a special bit pattern).

My guess is that the second application does not actually perform a division by zero, but rather a division with a really small number. You can check this by inspecting the underlying representation, either in a debugger or by trace output (you can access it by placing it in a union of the floating-point type and an integer of the same size). Note that simply printing it might not reveal this, as the print algorithm sometimes print really small numbers as zero.

Lindydancer
  • 25,428
  • 4
  • 49
  • 68