> 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
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
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
n of
R7RS, which happened more than ten years ago.
OK.
I agree with the last point; a future RnRS can special-case "(srfi N)",
demanding that the library described by it must be the same as the
library "(srfi :N)". The latter would be the default and numbers in
libr
less, the fact
> is that there are two widespread existing conventions. We should make
> them interoperate.
>
I agree with the last point; a future RnRS can special-case "(srfi N)",
demanding that the library described by it must be the same as the library
"(srfi :N)". The latter would be the default and numbers in library names
otherwise deprecated. Numbers would be reserved for versioning.
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
to use the first library name part
> instead of the last is the only technical obstacle to numbers in library
> names, it seems the cost is trivial.
>
There are other costs involved, e.g., when mappings from library names to
the pathnames have to be specified. While it is straightforward
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 <m...@aartaka.me>:Hi y'all,
I've been confused by the statements that R6/7RS don&#
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
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/r
>> 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
in library
names, it seems the cost is trivial.
Why not take the first library name part instead of the last?
The last name part is the most specific one.
What does that mean, and what are the ramifications?
the R7RS authors were
likely unaware of the incompatibility of their proposal
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
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).
Where does the decision to take the last library name part come from?
14 matches
Mail list logo
