From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Copy-on-write strings and mutation-sharing strings
Date: Sun, 22 Aug 2004 11:33:48 +1000 [thread overview]
Message-ID: <871xi03qir.fsf@zip.com.au> (raw)
In-Reply-To: ljsmajt0cf.fsf@troy.dt.e-technik.uni-dortmund.de
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.
Changing scm_substring to use scm_i_substring_copy makes it better, if
that helps suggest a cause.
_______________________________________________
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 1:33 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 [this message]
2004-08-22 7:44 ` Marius Vollmer
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=871xi03qir.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).