Re: Anonymous records Antero Mejr (30 Sep 2024 02:45 UTC)
Re: Anonymous records Marc Nieper-Wißkirchen (30 Sep 2024 06:02 UTC)
Re: Anonymous records Daphne Preston-Kendal (30 Sep 2024 07:08 UTC)
Re: Anonymous records Marc Nieper-Wißkirchen (30 Sep 2024 07:30 UTC)
Re: Anonymous records Daphne Preston-Kendal (30 Sep 2024 07:46 UTC)
Re: Anonymous records Antero Mejr (30 Sep 2024 19:26 UTC)
Re: Anonymous records Daphne Preston-Kendal (30 Sep 2024 20:12 UTC)
Re: Anonymous records Sergei Egorov (30 Sep 2024 21:07 UTC)
Re: R7RS large primitives [was: Re: Anonymous records] Antero Mejr (02 Oct 2024 22:28 UTC)
Re: R7RS large primitives [was: Re: Anonymous records] Sergei Egorov (02 Oct 2024 23:17 UTC)
Re: Anonymous records Wolfgang Corcoran-Mathe (01 Oct 2024 00:58 UTC)
Re: Anonymous records Antero Mejr (01 Oct 2024 03:24 UTC)
Re: Anonymous records Arthur A. Gleckler (01 Oct 2024 03:46 UTC)
Scheme meetups [was: Re: Anonymous records] Peter Bex (01 Oct 2024 19:20 UTC)
Re: Anonymous records Retropikzel (07 Oct 2024 16:14 UTC)
Re: Anonymous records Peter Bex (07 Oct 2024 18:01 UTC)
Re: Anonymous records Arthur A. Gleckler (07 Oct 2024 19:57 UTC)

Re: Anonymous records Retropikzel 07 Oct 2024 15:10 UTC

This is little bit off topic, sorry about that.

On 30/09/2024 22:26, Antero Mejr wrote:

 > 1. It's uniquely annoying to write portable Scheme, because each
 >   implementation has inconsistent library support.

I'm glad you want to write portable code. I also want to do that. If
youd like to help making it less annoying there are some projects. See
3. and 4.

 > 2. In order to find documentation for writing portable Scheme,
 > you need to consult at least 3 different websites simultaneously (the
 > standard, SRFIs, implementation).

If you were using some other language you would consult the language
and library documentation. So only one place less than with Scheme. And
dont worry, the standard will become second nature in no time.

There is also the Scheme index which could make things easier:
https://index.scheme.org/

> 3. No reference implementations, so lots of duplication of work. The
>     SRFI examples often are not portable (especially the older ones), and
>     need to be put together piecemeal, because there is no standard for
>     package management.
>

There is project to collect/implement/gather/hack SRFI implementations
as portable R7RS libraries. https://github.com/srfi-explorations/r7rs-srfi

Any help is very much appreciated! :)

> 4. The largest program written in Scheme, the Guix package manager, does
>     not have a way to install or (re)use R7RS libraries, ironically.
>
Guix is mostly a Guile project and I think it makes sense they
prioritise their own implementation. That said I also use Guix and I
took a crack at making a Guix channel out of snow-fort.org packages last
sunday and managed to get it to work locally with Guix shell.

https://gitea.scheme.org/Rinne/snow-fort-guix-channel

It still does not work guix pull, and I need to figure out how to let
users install the SRFI libraries of their choice but for one days work
I'd say it's half a decent. Help with this is also appreciated. Like the
Guile people you can scracth your own itch.

Unfortunately I don't think there is a good mailing list to discuss
projects in general, there are some on
https://srfi.schemers.org/srfi-list-subscribe.html but it says they are
for discussion that is hoped to lead to SRFI. Which is understandable.
I'm thinking about a solution but it is still in very early stage. So if
you (or anyone else reading this) are interested in helping in these
projects do not hesitate to email me. Github issues and pull requests
also appreciated and gitea and jenkins accounts can be made when needed.