bug#73605: [PATCH] Replace SRFI-64 with a new implementation.

2024-10-21 Thread Tomas Volf
Ludovic Courtès  writes:

> Tomas, I leave you the satisfaction of closing all the SRFI-64 bugs.
> :-)

Thank you for merging the patch, I am off to close the bug reports :)

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.


signature.asc
Description: PGP signature


bug#72547: [PATCH 3/9] tests: Skip hole-related port tests on Darwin.

2024-10-21 Thread Tomas Volf
Ludovic Courtès  writes:

> Tomas Volf <~@wolfsden.cz> skribis:
>
>> +(define (skip-on-darwin)
>> +  (when (string-ci=? "darwin" (vector-ref (uname) 0))
>> +(throw 'untested)))
>
> I changed (vector-ref (uname) 0) to (utsname:sysname (uname)) in this
> and other patches.

I am of course fine with the change, but I am pretty sure I just
copy-pasted it from either test-suite/standalone/test-out-of-memory or
test-suite/standalone/test-stack-overflow.

>
> (We might want to factorize this procedure.  :-))

Will put that on the todo list.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.


signature.asc
Description: PGP signature


bug#32841: assoc-set fails with dot notation association list

2024-10-21 Thread ���п�
The thread and all replies were in 2018. Six years later, in 2024, Anyone 
opening the up-to-date online manual still sees the old bad code there! The 
manual is not adjusted even though previous emails had pointed the cause and 
solution out!
Today, the page has a valid link of  
https://www.gnu.org/software/guile/manual/html_node/Alist-Example.html  and still
 contains

 6.6.20.6  Alist Example

Here is a longer example of how alists may be used in practice.
(define capitals '(("New York" . "Albany")("Oregon"   . 
"Salem")("Florida"  . "Miami"))) ;; What's the capital of 
Oregon? (assoc "Oregon" capitals)   ?6?0 ("Oregon" . "Salem") (assoc-ref 
capitals "Oregon")   ?6?0 "Salem" ;; We left out South Dakota. (set! capitals   
(assoc-set! capitals "South Dakota" "Pierre")) capitals ?6?0 (("South 
Dakota" . "Pierre") ("New York" . "Albany") ("Oregon" . "Salem") 
("Florida" . "Miami")) ;; And we got Florida wrong. (set! capitals   
(assoc-set! capitals "Florida" "Tallahassee")) capitals ?6?0 (("South Dakota" . 
"Pierre") ("New York" . "Albany") ("Oregon" . "Salem") ("Florida" . 
"Tallahassee")) ;; After Oregon secedes, we can remove it. (set! capitals   
(assoc-remove! capitals "Oregon")) capitals ?6?0 (("South Dakota" . "Pierre")   
  ("New York" . "Albany") ("Florida" . "Tallahassee"))



 

  

  
??

bug#73605: [PATCH] Replace SRFI-64 with a new implementation.

2024-10-21 Thread lloda
I'm pleased to see all these fixes. However, I noticed a few breakages. They 
come from relying on undocumented behavior, but only using the public 
interface, so others might be affected. I don't propose to patch them, but 
perhaps to make a note in NEWS or (for the last two) to add a paragraph in the 
manual explaining how to achieve the same goal – the reference documentation 
doesn't have enough examples.

* test-begin and test-end now require strings. The old version accepted symbols.
* test-approximate requires real arguments. The old version accepted complex 
arguments.
* The exported variable test-log-to-file is gone.






bug#32841: assoc-set fails with dot notation association list

2024-10-21 Thread ���п�
The thread and all replies were in 2018. Six years later, in 2024, Anyone 
opening the up-to-date online manual still sees the old bad code there! The 
manual is not adjusted even though previous emails had pointed the cause and 
solution out!
Could anyone take action to edit  api-data.texi  in guile's 
git savannah repo by replacing the bad code in @node Alist Example to a good 
one, using list and cons instead of directly quoting?



  
??

bug#32841: assoc-set fails with dot notation association list

2024-10-21 Thread Tomas Volf
".%c2.п." via "Bug reports for GUILE, GNU's Ubiquitous
Extension Language"  writes:

> The thread and all replies were in 2018. Six years later, in 2024, Anyone 
> opening the up-to-date online manual still sees the old bad code there! The 
> manual is not adjusted even though previous emails had pointed the cause and 
> solution out!
> Today, the page has a valid link of  
> https://www.gnu.org/software/guile/manual/html_node/Alist-Example.html  and still
>  contains
>
>  6.6.20.6  Alist Example
>
> Here is a longer example of how alists may be used in practice.
> (define capitals '(("New York" . "Albany")("Oregon"   . 
> "Salem")("Florida"  . "Miami"))) ;; What's the capital of 
> Oregon? (assoc "Oregon" capitals)   ⇓ ("Oregon" . "Salem") (assoc-ref 
> capitals "Oregon")   ⇓ "Salem" ;; We left out South Dakota. (set! capitals
>(assoc-set! capitals "South Dakota" "Pierre")) capitals ⇓ (("South Dakota" 
> . "Pierre") ("New York" . "Albany") ("Oregon" . "Salem") 
> ("Florida" . "Miami")) ;; And we got Florida wrong. (set! capitals   
> (assoc-set! capitals "Florida" "Tallahassee")) capitals ⇓ (("South Dakota" . 
> "Pierre") ("New York" . "Albany") ("Oregon" . "Salem") ("Florida" 
> . "Tallahassee")) ;; After Oregon secedes, we can remove it. (set! capitals   
> (assoc-remove! capitals "Oregon")) capitals ⇓ (("South Dakota" . 
> "Pierre") ("New York" . "Albany") ("Florida" . "Tallahassee"))
>
>
>
>  
>
>   
> 深圳大学  
> 
> 陈
> 有骏

Your message is really hard to read, I cannot make heads or tails of the
formatting.  Could you please resend it formatted in a normal way?  In
particular, wrapping your text to 72 characters and properly formatting
the code example will improve the readability a lot.

Have a nice day,
Tomas Volf

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.





bug#71262: Status: [PATCH] Try to install C.UTF-8 locale before falling back to C.

2024-10-21 Thread Tomas Volf
"Dr. Arne Babenhauserheide"  writes:

> Tomas Volf <~@wolfsden.cz> writes:
>
>> Does anyone has any opinion regarding this?  I think it is sensible
>> default in the year 2024.
>
> I like the idea — I just don’t know enough of the platforms where Guile
> is used (like embedded tools / tiny computers?) to know whether there is
> danger in doing so.

I am pretty sure there should not be any (I know I know, famous last
words).  If the installation of the locale fail, it falls back to the
previous behavior.  I would hope this patch can only improve things.

Tomas


signature.asc
Description: PGP signature