RE: Numbers in library names

> If (srfi |1|) were to be standardised via SRFI process or RnRS (maybe > implicitly as a ‘module names equality is to be done modulo > number/symbol conversions’ thing in a future R8RS), then (srfi |1|) > would be fine, but such a thing. Looks like I didn’t finish the sentence: ‘but such a thi

Re: Numbers in library names

I haven’t received the e-mail you are responding too (in particular, I don’t know who you are responding to), but … I was talking to Marc; it seems there is a delay in list traffic. As already has been answered: The practical harm is (srfi |1|) is non-standard, but it looks standard because

RE: Numbers in library names

I haven’t received the e-mail you are responding too (in particular, I don’t know who you are responding to), but … >> In R7RS, (srfi 1) and (srfi |1|) are different library names. > >What is the practical harm? > >(If there is some obscure point whereby the semantics don't add up in an intuitiv

Re: Numbers in library names

In R7RS, (srfi 1) and (srfi |1|) are different library names. What is the practical harm? (If there is some obscure point whereby the semantics don't add up in an intuitive way, I would genuinely like to hear about it. In practice, I think library aliases will be a must-have feature eventuall

Re: Numbers in library names

Am Di., 23. Juli 2024 um 17:06 Uhr schrieb Lassi Kortela : > > There are other costs involved, e.g., when mappings from library names > > to the pathnames have to be specified. While it is straightforward to > > encode a number of characters like "/" or ":", it is not so > > straightforward to enc

Re: Numbers in library names

There are other costs involved, e.g., when mappings from library names to the pathnames have to be specified. While it is straightforward to encode a number of characters like "/" or ":", it is not so straightforward to encode numbers differently from symbols that look like numbers. Why would

Re: Numbers in library names

Am Mo., 22. Juli 2024 um 20:13 Uhr schrieb Lassi Kortela : > > As I wrote, this is a syntactic extension of Chez Scheme - but a very > > useful one - and outside of the R6RS. The Unsyntax expander I wrote > > also implements it. > > If patching these two implementations to use the first library n

Re: Numbers in library names

Hi Marc,Yes, that clarifies a lot, thank you!—Artyom Bologovhttps://aartaka.meOn 23 Jul 2024, at 01:02, Marc Nieper-Wißkirchen wrote:Am Mo., 22. Juli 2024 um 22:52 Uhr schrieb Artyom Bologov :Hi y'all, I've been confused by the statements that R6/7RS don't have numbers in librar

Re: Numbers in library names

Am Mo., 22. Juli 2024 um 22:52 Uhr schrieb Artyom Bologov : > Hi y'all, > > I've been confused by the statements that R6/7RS don't have numbers in > library names. Because both kinda do. > > R6RS seems to allow the last library name element to be a list (?) of > numbers explicitly reserved for lib

Re: Numbers in library names

Hi y'all, I've been confused by the statements that R6/7RS don't have numbers in library names. Because both kinda do. R6RS seems to allow the last library name element to be a list (?) of numbers explicitly reserved for library version: See https://www.r6rs.org/final/html/r6rs/r6rs-Z-H-10.html

RE: Numbers in library names

>> the R7RS authors were >> likely unaware of the incompatibility of their proposal to allow numeric >> name parts with existing implementations and language extensions. > >Implementation, singular. Implementations, plural, since Chibi seems to do the same ‘module name -> file name’ thing as Gu

Re: Numbers in library names

As I wrote, this is a syntactic extension of Chez Scheme - but a very useful one - and outside of the R6RS.  The Unsyntax expander I wrote also implements it. If patching these two implementations to use the first library name part instead of the last is the only technical obstacle to numbers

Re: Numbers in library names

Am Mo., 22. Juli 2024 um 19:43 Uhr schrieb Lassi Kortela : > > To correctly attach marks (in the R6RS syntax model) to the imported > > identifiers, the expander needs marks associated with the library name > > (and takes the marks of the last name part, which, therefore, must be an > > identifier