public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Charles <chturne@gmail.com>
To: Sudarshan S Chawathe <chaw@eip10.org>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: Q about format's behavior with ~R directive
Date: Thu, 4 Feb 2021 23:41:36 +0000	[thread overview]
Message-ID: <CAPMhJv2Ze41zWPZjJBnh6n+LFWEhJ0vvD4vN=rEny81SxQedtQ@mail.gmail.com> (raw)
In-Reply-To: <16367.1612474498@localhost>

Hi,

On Thu, Feb 4, 2021 at 10:33 PM Sudarshan S Chawathe <chaw@eip10.org> wrote:

> With the code
>
>   (format #t "~R~%" 100)
>
> I get
>
>   hundred
>
> but with the Common Lisp equivalent (I think)
>
>   (format t "~R~%" 100)
>
> in SBCL I get instead
>
>   one hundred
>
> I am unsure of how tightly specified any of this is, but to me the SBCL
> output makes more sense.  Is this expected, allowed, by design, a
> bug, or something else?


There isn't a specification to my knowledge on the specific language used
to count the numbers, although in this case Kawa is an oddity. I attached a
patch to fix that. The testsuite errors for me from a fresh git clone and
it's been a while since I've contributed, so I don't know if it breaks in
other areas aside from the obvious formatting cases.




>
>
> 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?
>
>
I don't know, but I would guess it's another under specified area, for the
the english number formatting in particular,


  // Inspired by the Slib version, which is inspired
  // by Bruno Haible's CLisp function format-small-cardinal.


-- 
Kind regards,
  Charles.

  reply	other threads:[~2021-02-04 23:41 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 [this message]
2021-02-04 23:42   ` Charles
2021-02-05  1:04     ` Per Bothner
2021-02-05  0:09 ` Per Bothner

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='CAPMhJv2Ze41zWPZjJBnh6n+LFWEhJ0vvD4vN=rEny81SxQedtQ@mail.gmail.com' \
    --to=chturne@gmail.com \
    --cc=chaw@eip10.org \
    --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).