The R7RS reference version and define-optionals Shawn Wagner (20 Apr 2023 11:45 UTC)
Library names and sublibrary names Lassi Kortela (20 Apr 2023 12:01 UTC)
Re: Library names and sublibrary names Shawn Wagner (20 Apr 2023 12:06 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (21 Apr 2023 07:45 UTC)
Re: Library names and sublibrary names John Cowan (22 Apr 2023 03:00 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 05:37 UTC)
Re: The R7RS reference version and define-optionals Arthur A. Gleckler (22 Apr 2023 23:02 UTC)

Re: Library names and sublibrary names Marc Nieper-Wißkirchen 21 Apr 2023 07:44 UTC

Am Do., 20. Apr. 2023 um 14:01 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:
>
>
> > The specification says that define-optionals and define-optionals* are
> > supposed to be provided in the (srfi 227 definition) library, which is
> > missing. The forms are defined in the source, but not used. There's an
> > old open pull request that adds exports for them from (srfi 227)
> > instead of adding the sublibrary.
> >
> > The R6RS version does provide them in its equivalent library.
>
> Sublibraries for SRFIs are problematic in that they share the same
> namespace as the "library names" we have been accumulating ever since
> SRFI 97 (SRFI Libraries).

The way SRFI 227 does it is not problematic.  The sublibrary names are
all prefixed by (srfi 227 ...) in the case of R7RS and by (srfi :227
opt-lambda ...) in case of R6RS.  The latter follows SRFI 97.  There
is not reason why R7RS should not adopt SRFI 97 as well.

Marc