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.
si
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 wi
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://w
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 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
".%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
"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 computer
