From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Worrying development
Date: Sat, 24 Jan 2004 01:27:51 +0100 [thread overview]
Message-ID: <87r7xqqjg8.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200401232218.OAA27477@morrowfield.regexps.com> (Tom Lord's message of "Fri, 23 Jan 2004 14:18:25 -0800 (PST)")
Tom Lord <lord@emf.net> writes:
> > I'd say that the real 'trouble' is that strings are mutable at
> > all.
>
> Worried mostly about variable-length character encodings in string?
> Or you'd just rather be programming in an ML-family language? :-)
Heh, no, I'm not really worried, I was actually trying to comment
Dirk's concerns.
> > Also, I still like the idea of using mutation-sharing substrings as
> > markers that allow O(1) access into variable-width encoded strings.
>
> Interesting. The interaction with STRING-SET! will be tricky. I
> think you'll either have to "timestamp" strings (one tick per mutation
> -- and you'll likely have to use a GC'ed value rather than an inline
> integer for timestamps) or wind up with O(K) for mutations where K is
> the number of shared substrings.
Yes. What I have in mind is that accessing strings is efficient as
long as no mutations are performed. I.e., instead of indication
positions in a string with an integer index, you create a shared
substring that starts at the desired position. (This could be done
with COW substrings, tho.)
> > Also, there is the possibility on the horizon that we turn
> > string-ref etc into 'primitive generics' which means that people
> > could implement new kinds of strings using GOOPS.
>
> Well, heck. In that case, maybe consider what I'm planning for Pika
> (at least initially). Purely ASCII strings are stored 1-byte per
> character. Most other strings 2-bytes per character. Strings using
> characters outside the Basic Multilingual Plane, 4 bytes per
> character.
Yes, that's an attractive approach. But I also find simply using
UTF-8 exclusively very attractive. It might fit better with what
other people are doing and we might need fewer conversions when
wrapping external libraries. Or maybe not.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-24 0:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 9:41 Worrying development Roland Orre
2004-01-16 11:19 ` Thien-Thi Nguyen
2004-01-16 11:34 ` Roland Orre
2004-01-24 22:44 ` Thien-Thi Nguyen
2004-01-16 11:59 ` tomas
2004-01-18 21:05 ` Marius Vollmer
2004-01-18 21:58 ` Tom Lord
2004-01-22 16:11 ` Dirk Herrmann
2004-01-22 18:26 ` Shared Substrings [was: Worrying development] Robert Uhl
2004-01-22 18:42 ` Worrying development Tom Lord
2004-01-23 11:45 ` Dirk Herrmann
2004-01-23 17:16 ` Tom Lord
2004-01-23 21:01 ` Marius Vollmer
2004-01-23 22:18 ` Tom Lord
2004-01-24 0:27 ` Marius Vollmer [this message]
2004-01-24 0:53 ` Tom Lord
2004-01-23 22:28 ` Paul Jarc
2004-01-24 12:09 ` rm
2004-01-24 13:29 ` Marius Vollmer
2004-01-26 2:42 ` overriding car/cdr (was: Worrying development) Paul Jarc
2004-02-08 16:21 ` overriding car/cdr Dirk Herrmann
2004-02-08 18:09 ` Marius Vollmer
2004-02-08 20:56 ` Paul Jarc
2004-03-20 22:28 ` Marius Vollmer
2004-03-22 17:05 ` David Van Horn
2004-03-22 21:03 ` Marius Vollmer
2004-03-22 17:24 ` Paul Jarc
2004-01-23 22:37 ` Worrying development Dirk Herrmann
2004-01-23 23:25 ` Tom Lord
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=87r7xqqjg8.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).