Email list hosting service & mailing list manager

Making SRFI implementations easier to use Lassi Kortela (01 Nov 2019 17:19 UTC)
Re: Making SRFI implementations easier to use John Cowan (01 Nov 2019 18:14 UTC)
Re: Making SRFI implementations easier to use Lassi Kortela (01 Nov 2019 18:21 UTC)
Re: Making SRFI implementations easier to use John Cowan (01 Nov 2019 18:33 UTC)
Re: Making SRFI implementations easier to use Lassi Kortela (01 Nov 2019 18:42 UTC)
Re: Making SRFI implementations easier to use Arthur A. Gleckler (01 Nov 2019 19:31 UTC)
Re: Making SRFI implementations easier to use Arthur A. Gleckler (01 Nov 2019 19:34 UTC)

Making SRFI implementations easier to use Lassi Kortela 01 Nov 2019 17:19 UTC

As a reader and tester of SRFIs, I'd like to make a small suggestion.

It would be nice if the Implementation section in each SRFI had:

- A list of the Scheme implementations on which the sample
implementation has been tested.

- Caveats, instructions and/or a small shell script to run the tests
and/or examples on each tested implementation. (These can just as well
go into the source code directory itself.)

- A link to the GitHub repo:
<github.com/scheme-requests-for-implementation/srfi-nnn>. It's clearest
if the link text shows that URL. Then each link reinforces our
understanding that the sample implementations live in the same GitHub
repos as the SRFI documents.

- A link to a tar file of the source code can be useful, but is there an
automated system that keeps those tar files up to date? The advantage of
linking to the Git repo is that it's guaranteed to have all errata
corrections. URLs of the form
<https://github.com/scheme-requests-for-implementation/srfi-nnn/archive/master.tar.gz>
can be used to get tar files of the latest master branch from GitHub.
That archive generates a normal archive file and the person downloading
it does not need to have Git installed.

These small additions would make it faster to understand and test
things. Thoughts?