Email list hosting service & mailing list manager

Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 04:28 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 05:50 UTC)
Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 06:26 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 06:46 UTC)
Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 06:59 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 07:17 UTC)
Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 07:35 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 08:31 UTC)
Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 09:01 UTC)
Re: Library names and sublibrary names John Cowan (22 Apr 2023 09:21 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 09:38 UTC)
Re: Library names and sublibrary names Lassi Kortela (22 Apr 2023 10:04 UTC)
Re: Library names and sublibrary names Marc Nieper-Wißkirchen (22 Apr 2023 10:17 UTC)

Re: Library names and sublibrary names Lassi Kortela 22 Apr 2023 04:28 UTC

[Moving the thread to srfi-discuss since it's no longer about SRFI 227.]

> you have to call them (srfi <number> <srfi-name> <library-hame>); you
> can't omit the supposedly optional <srfi-name>.

A decision should be made about that. Does (srfi <number>
<sublibrary-name>) make sense or not, given that (srfi <number>
<srfi-name>) exists?

> Of course if we had keywords in library names ....

We already kind of do. In R6RS we use (import (srfi :123)). It's wise to
prepare for a scenario where R6RS and R7RS are merged, and some of the
implementations additionally support keywords with : prefix syntax.

Then we'll have some implementations in the wild that parse the :123 as
a keyword and others that parse it as a symbol. It's may be prudent to
treat keywords the same as symbols while dropping the "#:" prefix, ":"
prefix, or ":" suffix. Common Lisp already does something like this in
common usage of `defpackage`. Uninterned symbols "#:" are treated the
same as keywords ":". Only the symbol name is considered.