Bug in SRFI 1 implementation
Chris Hanson
(27 May 2020 02:56 UTC)
|
Re: Bug in SRFI 1 implementation
Chris Hanson
(27 May 2020 03:04 UTC)
|
Re: Bug in SRFI 1 implementation
Alex Shinn
(27 May 2020 04:23 UTC)
|
Re: Bug in SRFI 1 implementation
Shiro Kawai
(27 May 2020 09:53 UTC)
|
Re: Bug in SRFI 1 implementation
Arthur A. Gleckler
(28 May 2020 00:09 UTC)
|
Re: Bug in SRFI 1 implementation
Alex Shinn
(28 May 2020 00:18 UTC)
|
Re: Bug in SRFI 1 implementation
Arthur A. Gleckler
(28 May 2020 01:59 UTC)
|
Re: Bug in SRFI 1 implementation
Alex Shinn
(28 May 2020 02:53 UTC)
|
Re: Bug in SRFI 1 implementation
John Cowan
(28 May 2020 14:37 UTC)
|
Re: Bug in SRFI 1 implementation
Marc Nieper-Wißkirchen
(28 May 2020 14:55 UTC)
|
Re: Bug in SRFI 1 implementation
John Cowan
(28 May 2020 17:40 UTC)
|
Re: Bug in SRFI 1 implementation Marc Nieper-Wißkirchen (02 Jun 2020 09:50 UTC)
|
Re: Bug in SRFI 1 implementation
Arthur A. Gleckler
(02 Jun 2020 17:22 UTC)
|
Re: Bug in SRFI 1 implementation
Arthur A. Gleckler
(02 Jun 2020 22:53 UTC)
|
Am Do., 28. Mai 2020 um 19:40 Uhr schrieb John Cowan <xxxxxx@ccil.org>: > The future is longer than the past (at least we hope so), but it's the past that controls the present, and the present is a lot of unadapted or minimally adapted copies of SRFI 1. Of course, one hopes that the predicate is usually an equivalence relation, in which case the bug does not matter. But when it isn't, the user will read the SRFI, try to use the procedure, fail, and complain. Changing the SRFI with a warning heads off a lot of complaints. Adding a warning, updating the sample implementation and asking maintainers of active Scheme implementations to check their code (this can be a joint effort by every one of us) seems like a good idea. This issue won't be the last one where not 100% bugfree (impossible, I'd say) sample implementations of (other) SRFIs have been used.