From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: Re: Q about format's behavior with ~R directive
Date: Thu, 4 Feb 2021 16:09:57 -0800 [thread overview]
Message-ID: <a62a129e-14b6-27f6-4189-bf0c6721ec20@bothner.com> (raw)
In-Reply-To: <16367.1612474498@localhost>
On 2/4/21 1:34 PM, Sudarshan S Chawathe wrote:
> A related question: Is it correct that Kawa uses SLIB's test file for
> format (formatst.scm in testsuite) but not SLIB's implementation of
> format?
Of course. If there is a new implementation of an interface,
it is even more valuable to test it with the old implementation's
tests, to get an understanding of the difference between the
implementations, such as what differences are bugs, intentional,
or otherwise acceptable.
In any case, it is (almost) impossible to have too many tests. The
Kawa testsuite includes tests from all kinds of sources.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2021-02-05 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 21:34 Sudarshan S Chawathe
2021-02-04 23:41 ` Charles
2021-02-04 23:42 ` Charles
2021-02-05 1:04 ` Per Bothner
2021-02-05 0:09 ` Per Bothner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a62a129e-14b6-27f6-4189-bf0c6721ec20@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
/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).