From: Per Bothner <per@bothner.com>
To: srfi-140@srfi.schemers.org, Kawa mailing list <kawa@sourceware.org>
Subject: srfi-140 (immutable strings) - getting close to last call
Date: Wed, 26 Apr 2017 21:33:00 -0000 [thread overview]
Message-ID: <209edb5c-4962-2a47-7341-1871794403a9@bothner.com> (raw)
The specification has been updated:
https://srfi.schemers.org/srfi-140/srfi-140.html
The most important changes:
- A redone and greatly expanded Implementation section.
- Link to a test suite.
- Renamed string-replicate to xsubstring, to match SRFI-13.
- Added unintentionally-skipped string-pad{,right} and string-trim{,-right,-both}.
The Kawa implementation is complete (barring bugs and testing) and seems
to be working well. So far very little Scheme code is broken by the
switch to immutable strings, but more testing would be welcome. When testing,
please replace (import (scheme base)) by (import (kawa base)) to make
sure you get the istring-returning procedures.
The implementation is in the 'invoke' branch of the Kawa repository:
https://gitlab.com/kashell/Kawa/tree/invoke
The plan is before finalization to have a final kawa 2.4 release, and then
merge the invoke branch into master. (This will becomes kawa 3.0 in the near future.)
The documentation for the 'invoke' branch is here:
http://per.bothner.com/kawa/invoke/index.html
The updated strings chapter is here:
http://per.bothner.com/kawa/invoke/Strings.html
To do before finalization:
- Add some more tests, including testing for srfi-118 features,
and more non-BMP-characters.
- Merge the Kawa invoke branch into master.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
reply other threads:[~2017-04-26 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=209edb5c-4962-2a47-7341-1871794403a9@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=srfi-140@srfi.schemers.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).