From: Mark H Weaver <mhw@netris.org>
To: OKUMURA Yuki <mjt@cltn.org>
Cc: 40584@debbugs.gnu.org
Subject: bug#40584: R7RS string-for-each does not work two or more strings on its argument
Date: Fri, 17 Apr 2020 17:07:14 -0400 [thread overview]
Message-ID: <87blnpu8gy.fsf@netris.org> (raw)
In-Reply-To: <CAG1-Us2+h_CkND26N5PQ4WC12kb85STR2Mtq+Kd9+beAcQg7QQ@mail.gmail.com>
OKUMURA Yuki <mjt@cltn.org> wrote:
> Actually it's my own bug but let me report here: (scheme base) lacks
> implementation for string-for-each thus following code does not work;
>
> (import (scheme base))
>
> (string-for-each
> (lambda (e f) 'ok)
> "01234"
> "slas")
>
> Please note that we already have incompatible string-for-each for
> SRFI-13 and R6RS.
> (It seems current (scheme base) uses SRFI-13 one)
> R7RS for-each (and map) procedures allow different length of
> collection as arguments.
>
> Checked on 2b4e45ca1b89a942200b7b9f46060dddc44d2876
For the record, the version of R7RS 'string-for-each' that I implemented
for Guile many years ago, in the 'r7rs-wip' branch of Guile's git
repository (not to be confused with 'wip-r7rs'), does not have this bug:
https://git.savannah.gnu.org/cgit/guile.git/tree/module/scheme/base.scm?h=r7rs-wip&id=2d76447bda2f3d61c94d80b3b78732648a0a511d#n221
I'm not sure why Andy chose not to use my work.
Mark
next prev parent reply other threads:[~2020-04-17 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 19:38 bug#40584: R7RS string-for-each does not work two or more strings on its argument OKUMURA Yuki
2020-04-17 21:07 ` Mark H Weaver [this message]
2021-05-12 21:03 ` Taylan Kammer
2023-09-29 17:01 ` bug#40584: lloda
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=87blnpu8gy.fsf@netris.org \
--to=mhw@netris.org \
--cc=40584@debbugs.gnu.org \
--cc=mjt@cltn.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).