Xref: utzoo comp.os.msdos.programmer:2944 alt.msdos.programmer:2367
Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!news.funet.fi!hydra!cc.helsinki.fi!teittinen
From: teittinen@cc.helsinki.fi
Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer
Subject: Re: Trapping Floating Point Errors in Turbo C
Message-ID: <1991Jan24.125150.4631@cc.helsinki.fi>
Date: 24 Jan 91 12:51:50 GMT
References: <21650@netcom.UUCP>
Organization: University of Helsinki
Lines: 14

In article <21650@netcom.UUCP>, resnicks@netcom.UUCP (Steve Resnick) writes:
> 
> I have a problem - I need to trap floating point errors from the floating
> point hardware. Currently, I am using signal() to do this, but signal doesn't
> give me some of the information I need.

Have you tried writing your own matherr()-function. It is another "clean"
way to handle floating point errors and it gets some information that is
not included in signal (if my memory serves me right).

-- 
E-Mail: teittinen@finuh.bitnet               ! "Studying is the only way
        teittinen@cc.helsinki.fi             !  to do nothing without
Marko Teittinen, student of computer science !  anyone blaming you" -me