|
The last SRFI 144 issue: flround
John Cowan
(16 Jul 2017 00:06 UTC)
|
|
Re: The last SRFI 144 issue: flround
Arthur A. Gleckler
(16 Jul 2017 03:41 UTC)
|
|
Re: The last SRFI 144 issue: flround William D Clinger (18 Jul 2017 09:48 UTC)
|
|
Re: The last SRFI 144 issue: flround
John Cowan
(18 Jul 2017 15:11 UTC)
|
|
Re: The last SRFI 144 issue: flround
William D Clinger
(18 Jul 2017 17:27 UTC)
|
|
Re: The last SRFI 144 issue: flround
Marc Nieper-Wißkirchen
(18 Jul 2017 20:42 UTC)
|
|
Re: The last SRFI 144 issue: flround
Bradley Lucier
(21 Jul 2017 00:07 UTC)
|
|
Re: The last SRFI 144 issue: flround
John Cowan
(21 Jul 2017 01:23 UTC)
|
|
Re: The last SRFI 144 issue: flround
Arthur A. Gleckler
(21 Jul 2017 02:38 UTC)
|
|
Re: The last SRFI 144 issue: flround
Arthur A. Gleckler
(21 Jul 2017 03:37 UTC)
|
John Cowan wrote: > The purpose of SRFI 144 is to provide the same floating-point facilities to > the Scheme programmer that provides to the C programmer. > Unfortunately, there's one major collision: the flround procedure. There are at least four other collisions: flinteger-fraction flnormalized-fraction-exponent flremquo flloggamma > It's specified that wherever there is a reference to a C function in SRFI > 144, it supersedes the informative definition. Yes, but that sentence of SRFI 144 cannot be taken seriously. For one thing, it refers to "the Posix or C99 standards", which do not include the Bessel functions. More importantly, the four procedures listed above return two values, which is not possible in C. Taking the sentence seriously would require programmers to pass an extra argument to those procedures, as in their C versions, and the second result would be returned by modifying that extra argument. What's really going on in SRFI 144 is that the references to C equivalents, as described by Posix, C99, or XSI, are informative only; for more precise definitions, users and implementers must consult the prose of SRFI 144. Will