Last call for comments on SRFI 261: Portable SRFI Library Reference Arthur A. Gleckler (07 Oct 2025 00:45 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Marc Nieper-Wißkirchen (07 Oct 2025 05:41 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (07 Oct 2025 05:45 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Marc Nieper-Wißkirchen (07 Oct 2025 06:10 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (07 Oct 2025 11:56 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Marc Nieper-Wißkirchen (07 Oct 2025 12:07 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (08 Oct 2025 07:37 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Marc Nieper-Wißkirchen (08 Oct 2025 08:46 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (08 Oct 2025 14:45 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Marc Nieper-Wißkirchen (08 Oct 2025 15:25 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (08 Oct 2025 21:26 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Daphne Preston-Kendal (08 Oct 2025 14:39 UTC)
Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Peter McGoron (07 Oct 2025 14:55 UTC)

Re: Last call for comments on SRFI 261: Portable SRFI Library Reference Peter McGoron 07 Oct 2025 14:54 UTC

There are some minor editorial changes I emailed about last time that
have not been added to the SRFI. Is there no new draft?

I still believe that every SRFI should have an identifier associated
with it. Even if they don't export identifiers, they can be used in
`(features)`, `cond-expand`, a future SRFI for systematic reader syntax
toggling, etc.

Even in the absence of that, I would add into the SRFI text that library
names specified in the SRFI metadata or the SRFI text should be allowed
as <name>s.

I will defend `<name>-NNN` over `srfi-NNN <name>` because it would
probably be easier for tooling like autocomplete that is not
specifically designed for the SRFI namespace. Being forced to write out
the name of the SRFI (especially in cases in which it is long, like
`generators-and-accumulators`) to refer to sublibraries sounds
cumbersome to me.

-- Peter McGoron