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

*To*: Bradley Lucier <lucier@xxxxxxxxxxxxxxx>*Subject*: Re: Implementation of read-ieee-float64*From*: Marc Feeley <feeley@xxxxxxxxxxxxxxxx>*Date*: Fri, 9 Dec 2005 09:27:05 -0500*Cc*: Alex Shinn <alexshinn@xxxxxxxxx>, srfi-56@xxxxxxxxxxxxxxxxx, Gambit List <Gambit-list@xxxxxxxxxxxxxxxx>*Delivered-to*: srfi-56@xxxxxxxxxxxxxxxxx*In-reply-to*: <5FEEDB41-F863-44D0-A1BA-6F9B0BA81911@xxxxxxxxxxxxxxx>*References*: <DAD12F48-4E49-4B32-A29D-7CD3018C3E8B@xxxxxxxxxxxxxxx> <5fb7e0870512081912v7fd21074q3777d53c60a45822@xxxxxxxxxxxxxx> <5FEEDB41-F863-44D0-A1BA-6F9B0BA81911@xxxxxxxxxxxxxxx>

On 9-Dec-05, at 12:21 AM, Bradley Lucier wrote:

On Dec 8, 2005, at 9:12 PM, Alex Shinn wrote:On 12/7/05, Bradley Lucier <lucier@xxxxxxxxxxxxxxx> wrote:Gambit 4.0b15 fails some srfi-56 tests because the first instance of 2.0 is not 2; unfortunately, Gambit-C calculates (expt 2.0 -1074) as (/ (expt 2.0 1074))Hi, thanks for looking into this and getting it working with Gambit. The (expt 2.0 ...) form was there for the sake of Bigloo, for which (expt N -M) => 0 for all exact integers N, M > 1.This may not be unreasonable for an implementation withoutrationals, like bigloo, but perhaps it would be better to do aninexact expt in this case.Choosing between the lesser of two evil^H^H^H^Hbugs,I'm working on a new expt that trusts libm's pow function more ... Brad

Marc

**Follow-Ups**:**Re: Implementation of read-ieee-float64***From:*Bradley Lucier

**References**:**Implementation of read-ieee-float64***From:*Bradley Lucier

**Re: Implementation of read-ieee-float64***From:*Alex Shinn

**Re: Implementation of read-ieee-float64***From:*Bradley Lucier

- Prev by Date:
**Re: Implementation of read-ieee-float64** - Next by Date:
**Re: Implementation of read-ieee-float64** - Previous by thread:
**Re: Implementation of read-ieee-float64** - Next by thread:
**Re: Implementation of read-ieee-float64** - Index(es):