On Wed, Sep 23, 2009 at 02:53:31AM -0400, John Cowan wrote: > In particular, unless an implementer is willing to provide CLisp-style > software, immediate floats are a bad idea. They inevitably have fewer > bits than IEEE, and just chopping those bits to 0 quickly rather than > properly rounding introduces so much error that the results are useless.
Could you please explain this bit a little more? How does not having immediate floats work? Do I have to convert all of my filter coefficients to scaled integers? Is it really a stretch to actually include or refer to IEEE floating point standards? R6RS does. There are fairly well respected ways to represent IEEE floats as immetiate values. Cheers, -- Andrew _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
