library names Alex Shinn (19 Aug 2020 04:18 UTC)
Re: library names Marc Nieper-Wißkirchen (19 Aug 2020 05:24 UTC)
Re: library names Alex Shinn (19 Aug 2020 05:42 UTC)
Re: library names Marc Nieper-Wißkirchen (19 Aug 2020 06:06 UTC)
Ideas for library names; please contribute Marc Nieper-Wißkirchen (21 Sep 2020 06:49 UTC)
Re: Ideas for library names; please contribute John Cowan (21 Sep 2020 12:34 UTC)
Re: Ideas for library names; please contribute Marc Nieper-Wißkirchen (21 Sep 2020 12:42 UTC)
Re: Ideas for library names; please contribute John Cowan (21 Sep 2020 13:50 UTC)
Re: Ideas for library names; please contribute Marc Nieper-Wißkirchen (21 Sep 2020 14:13 UTC)

Re: Ideas for library names; please contribute Marc Nieper-Wißkirchen 21 Sep 2020 12:41 UTC

Am Mo., 21. Sept. 2020 um 14:34 Uhr schrieb John Cowan <xxxxxx@ccil.org>:

> I think $ has the same considerations as *, though not as strongly (* is outright forbidden on Windows).  In practice, anything more than ASCII lowercase letters and digits is a Bad Idea.  We should stick to lowercase because there are case-folding filesystems like FAT, NTFS, and APFS .  (In the last two it is possible to enable case-sensitivity, but most people don't.)

I didn't know that `$' has problems on some file systems.

> I prefer "auto" to "all", because "auto" suggests creation on the fly (as I assume will be the case) whereas "all" suggests the pre-existence of countably many identifiers.

Whether something is created on the fly or not, depends on the
implementation. From a user's perspective, there is actually the
illusion that countably many identifiers pre-exist. At least only
under this illusion, you know that you mustn't do [still using the old
name]

(import (srfi 206 *))

but can only [:-)] do

(import (only (srfi 206 *) foo bar quux))