RE: [PATCH] doc: Mention how to remove namespaces in xml->sxml.

2024-07-23 Thread Maxime Devos
>+@code{xml->sxml}. A namespace can be removed by using a @code{#f} custom >+prefix. > > @example > (xml->sxml "http://example.org/ns1\";>text") If you remove a single namespace, apparently that’s true, but what if multiple namespaces are removed? Does it still work then? (I can imagine that s

Re: Are library names data or syntax?

2024-07-23 Thread Marc Nieper-Wißkirchen
Am Mo., 22. Juli 2024 um 20:47 Uhr schrieb Maxime Devos < maximede...@telenet.be>: > > [...] > > > > > >In what kind of situation might a library name be made up of identifiers > (syntax objects) that might need to carry lexical information? > > > > As implied by the previous: never (in Guile, and

Re: [PATCH] doc: Mention how to remove namespaces in xml->sxml.

2024-07-23 Thread Dr. Arne Babenhauserheide
Maxime Devos writes: >> (xml->sxml "http://example.org/ns1\";>text") > If you remove a single namespace, apparently that’s true, but what if > multiple namespaces are removed? Does it still work then? Yes, it still works: (import (sxml simple)) (define xml-string "http://foobar\";>http://www.w

Re: Numbers in library names

2024-07-23 Thread 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 encode numbers differently from symbols that look like numbers. Why would

Re: Numbers in library names

2024-07-23 Thread Marc Nieper-Wißkirchen
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

2024-07-23 Thread Lassi Kortela
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

2024-07-23 Thread Maxime Devos
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

2024-07-23 Thread Lassi Kortela
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

2024-07-23 Thread Maxime Devos
> 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

Lexically bound macro, with lexically bound transformer

2024-07-23 Thread spacecadet
Hi, I didn't see a help-guile list, I hope this isn't out of place I'm trying to lexically bind a macro to a lexically bound transformer procedure (let ((outer (lambda (x) #''( (let-syntax ((inner outer)) inner)) This is producing an error "reference to identifier outside its scope in