From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: Copy-on-write strings and mutation-sharing strings
Date: Sun, 22 Aug 2004 09:44:15 +0200 [thread overview]
Message-ID: <87oel3ipm8.fsf@zagadka.ping.de> (raw)
In-Reply-To: <871xi03qir.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 22 Aug 2004 11:33:48 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>>
>> go crazy and try to break them!
>
> The build script (the scheme bit, not any C code) in the guile-gtk-1.2
> cvs exposes some breakage. It bombs in a string-ref, looking like
> taking a substring has caused truncation of the originating string,
> maybe.
Now that is embarassing! I got the substring operation totally wrong,
not taking into account that the substringed string might itself be a
substring.
I don't have time right now to fix it, but this is so embarrasing, I
must start blathering right away about how embarassing it is... should
be fixed today.
A simple test case is:
guile> (substring (substring "0123456789" 3) 0 4)
"0123"
The second substring gets a string with STRING_START != 0, which is
totally ignored. Also mutation-sharing substrings would crash Guile,
as in:
guile> (substring (substring/shared "0123456789" 3) 0 4)
"'\x02
\x00"
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-22 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 19:05 Copy-on-write strings and mutation-sharing strings Marius Vollmer
2004-08-20 1:33 ` Kevin Ryde
2004-08-20 10:49 ` Marius Vollmer
2004-08-22 1:52 ` Kevin Ryde
2004-08-22 1:33 ` Kevin Ryde
2004-08-22 7:44 ` Marius Vollmer [this message]
2004-08-22 1:34 ` Kevin Ryde
2004-08-24 17:21 ` Marius Vollmer
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=87oel3ipm8.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).