From: Per Bothner <per@bothner.com>
To: Kawa mailing list <kawa@sourceware.org>
Subject: kawa improvements for strings and sequences
Date: Fri, 12 Jun 2015 21:33:00 -0000 [thread overview]
Message-ID: <557B5001.2000500@bothner.com> (raw)
I checked in a number of neat features recently.
Check out the first few sections here:
http://www.gnu.org/software/kawa/news.html
The main still-missing functionality is replacement indexing:
(set! (seq [i <: j]) new-value)
This would generalize insertion/deletion/replacement.
I have prototype code for this (working for arbitrary java.util.List), but I
need to figure out how to detect and handle if new-value overlaps with seq.
Another issue still unresolved is how to print ranges and indirect-indexing:
#|kawa:1|# [3 <=: 6]
(#sequence 3 4 5 6)
I'm thinking this should display as: [3 4 5 6]
and write as: [3 <: 7]
#|kawa:2|# ([11 12 13 14] [3 2])
(#sequence 14 13)
This should probably print as: [14 13]
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next reply other threads:[~2015-06-12 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 21:33 Per Bothner [this message]
2015-06-12 23:53 ` Jamison Hope
2015-06-13 7:27 ` 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=557B5001.2000500@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).