[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IEEE float co-processors

To: Richard Fateman <fateman@dali.berkeley.edu>, Scott E. Fahlman <Fahlman@C.CS.CMU.EDU>, common-lisp@SU-AI.ARPA
Subject: IEEE float co-processors
From: David C. Plummer <DCP@SCRC-QUABBIN.ARPA>
Date: Tue, 28 Jan 86 10:45 EST
In-reply-to: <8601280708.AA04790@dali.berkeley.edu>, <FAHLMAN.12178838237.BABYL@C.CS.CMU.EDU>

I think I agree with what you two are talking about.  It is critical
that the answer be of the correct type.  We (Symbolics) used to have a
proceed option such that if a single float computation overflowed, the
user could continue using double floats.  We got rid of that after we
realized that was tempting users to believe they had more accuracy than
they actually had.  It all goes back to: If you are going to use
floating point, you better know what you are doing.

References:
- IEEE float co-processors
  - From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>

Prev by Date: DEFUN inside LET
Next by Date: IEEE float co-processors
Previous by thread: IEEE float co-processors
Next by thread: Re: IEEE float co-processors
Index(es):
- Date
- Thread