🚀 go-pugleaf

When checking for possible difficulty with division by zero, if you don't
wish to get into trapping overflow and the like, you should check at least
for small non-zero numbers.  If all your numerators have absolute value < 4,
you could safely do
#include <float.h>
if(fabs(y)>FLT_MIN)
    proceed with division by y
else
    treat as error

Depending on your problem, the problem you describe might occur far less
frequently if your variables were declared as double.
All your intermediate float operations will be performed in long double by
default, admitting non-zero working register values as small as LDBL_MIN.
"Rishabh Gupta" <rg117@ohm.york.ac.uk> wrote in message
news:clcm-20010905-0003@plethora.net...
> Hi all,
>     I've been getting really strange results in my program when I use very
> small float values. For example, I check for 0.0 in case of division by
zero
> errors but I still get the error. I also get other strange results
> like -0.0000...... (although I'm guessing that its just not displaying all
> the digits)
> My system is
>     Pentium II 500 Mhz, 128MB
>     Linux Mandrake 8.0
> I have checked my program repeatedly and I can't find anything wrong with
it
> (its not even very complicated). Could the problem be a bug in the
compiler
> (GCC) or is it just supposed to do this?
>
> If anyone can help I would be very greatful.
> Many Thanks!!
>
> Rishabh
> --
> comp.lang.c.moderated - moderation address: clcm@plethora.net
-- 
comp.lang.c.moderated - moderation address: clcm@plethora.net