From: Peter Lane <peter@peterlane.info>
To: kawa@sourceware.org
Subject: Re: [ANN] Some R7RS libraries
Date: Mon, 10 Apr 2017 18:45:00 -0000 [thread overview]
Message-ID: <002f0b2d-6228-648b-7197-d675225c8bd4@peterlane.info> (raw)
In-Reply-To: <bb9b821e-572b-7f35-6cc5-97c1e2c5325e@bothner.com>
On 10/04/17 18:21, Per Bothner wrote:
> Perhaps it would make sense to add SRFI-27 to Kawa itself.
I will take another look at it first but yes, it would be convenient to
add in to Kawa itself.
> Have you tested your library with the 'invoke' git branch?
> That would be valuable, as the invoke branch will become Kawa 3.x
> this year (the plan is to do so before JDK 9 is released).
I shall give that a try and let you know what happens.
> There are a number of incompatible changes, most notably that by
> default Kawa will follow SRFI-140, so most string procedures
> will return immutable strings.
That may need another cond-expand option in places. I have a few such
for strings already, as chibi does not support srfi 13.
--
Peter Lane
http://peterlane.info/scheme.html
next prev parent reply other threads:[~2017-04-10 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 14:07 Peter Lane
2017-04-10 17:21 ` Per Bothner
2017-04-10 18:45 ` Peter Lane [this message]
2017-04-10 19:11 ` 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=002f0b2d-6228-648b-7197-d675225c8bd4@peterlane.info \
--to=peter@peterlane.info \
--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).