delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:1051 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: acos(2.0) and other errors |
Date: | Mon, 12 Feb 1996 21:23:28 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 11 |
Message-ID: | <31200430.sandmann@clio.rice.edu> |
References: | <271654446E1 AT fs2 DOT mt DOT umist DOT ac DOT uk> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> I am sick of program runs being hostage to one stray floating point overflow. > What I want is one or both of (1) Being able to tell the PC to carry on > regardless if overflow happens, (2) Being able to tell the PC to go to such > and such an address if overflow happens. It already exists, it's standard, it's: signal() !!! Look in the info pages. With floating point you also have the option of modifying the floating point control, check the info pages for that information also.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |