Bug in srfi-48?
Donald Allen
(11 Oct 2017 19:42 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(11 Oct 2017 19:46 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(11 Oct 2017 20:36 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(11 Oct 2017 21:33 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(12 Oct 2017 13:04 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(12 Oct 2017 19:07 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(12 Oct 2017 19:42 UTC)
|
Re: Bug in srfi-48?
Shiro Kawai
(12 Oct 2017 20:40 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(12 Oct 2017 23:13 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(13 Oct 2017 02:09 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(13 Oct 2017 15:58 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(13 Oct 2017 16:13 UTC)
|
Re: Bug in srfi-48?
Marc Feeley
(13 Oct 2017 17:50 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(13 Oct 2017 17:52 UTC)
|
Re: Bug in srfi-48?
Shiro Kawai
(13 Oct 2017 19:54 UTC)
|
Re: Bug in srfi-48?
John Cowan
(13 Oct 2017 17:34 UTC)
|
Re: Bug in srfi-48? Donald Allen (13 Oct 2017 17:51 UTC)
|
Re: Bug in srfi-48?
Alex Shinn
(14 Oct 2017 13:03 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(14 Oct 2017 13:11 UTC)
|
Re: Bug in srfi-48?
Arthur A. Gleckler
(18 Oct 2017 18:20 UTC)
|
Re: Bug in srfi-48?
Donald Allen
(18 Oct 2017 19:11 UTC)
|
On 13 October 2017 at 13:33, John Cowan <xxxxxx@ccil.org> wrote: > > > On Fri, Oct 13, 2017 at 11:58 AM, Donald Allen <xxxxxx@gmail.com> > wrote: > >> I must say that it's disconcerting to be finding all these problems in >> code that was finalized in 2004. > > > Note that it is the SRFI prose, not the code, that is finalized. The code > is just sample code, and may have bugs like any other code. Indeed, the > requirement to provide tests is relatively recent and has not been made > retroactive. You know more about the srfi process than I do and I accept your explanation. Also, I thought the purpose of the srfis was to provide a library of useful functionality to be used in Scheme development, much like Haskell Hackage or the Rust crates.io. But from what you say, the code provided is not in the same category and use of it feels like beta-testing, at least for those srfis that pre-date the test requirement. > > Nor is there any guarantee that the sample code will Just Work on all > Schemes. Indeed, I just found a bug in my SRFI 158 test suite depending on > the fact that (/ 8) can evaluate to either 0.125 or 1/8, and that these are > not the same in the sense of `equal?`. I've been doing this long enough to understand that even mature code can have bugs. It's just the nature and quantity of the issues with srfi-48 that trouble me. I was intending to use this for generating a report that I rely on for assisting me in managing my finances, because I prefer working in Scheme. But it's hard to justify that now. Thanks for the feedback and enlightenment. /Don > > -- > John Cowan http://vrici.lojban.org/~cowan xxxxxx@ccil.org > Today an interactive brochure website, tomorrow a global content > management system that leverages collective synergy to drive "outside of > the box" thinking and formulate key objectives into a win-win game plan > with a quality-driven approach that focuses on empowering key players > to drive-up their core competencies and increase expectations with an > all-around initiative to drive up the bottom-line. --Alex Papadimoulis > >