From: "Ludovic Courtès" <ludo@gnu.org>
To: lloda <lloda@sarc.name>
Cc: Tomas Volf <~@wolfsden.cz>, 73605@debbugs.gnu.org
Subject: bug#73605: [PATCH] Replace SRFI-64 with a new implementation.
Date: Sat, 26 Oct 2024 15:21:40 +0200 [thread overview]
Message-ID: <875xpf0zkr.fsf@gnu.org> (raw)
In-Reply-To: <09A9A831-0334-4109-823D-71FF335EBA75@sarc.name> (lloda@sarc.name's message of "Mon, 21 Oct 2024 19:35:23 +0200")
Hi,
lloda <lloda@sarc.name> skribis:
> 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.
As discussed on IRC, I think we should consider restoring support for
these idioms, whether or not they conform to the reference, in an effort
to minimize breakage (especially since this is slated for a point
release).
WDYT, Tomas?
Ludo’.
next prev parent reply other threads:[~2024-10-26 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 19:27 bug#73605: [PATCH] Replace SRFI-64 with a new implementation Tomas Volf
2024-10-13 20:09 ` Ludovic Courtès
[not found] ` <87o73nrchr.fsf@gnu.org>
2024-10-20 19:24 ` Ludovic Courtès
2024-10-20 19:25 ` Ludovic Courtès
2024-10-21 17:35 ` lloda
2024-10-26 13:21 ` Ludovic Courtès [this message]
2024-10-26 14:09 ` Tomas Volf
2024-10-26 18:09 ` lloda
2024-10-21 20:15 ` Tomas Volf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xpf0zkr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=73605@debbugs.gnu.org \
--cc=lloda@sarc.name \
--cc=~@wolfsden.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).