From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Subject: bug in srfi-13
Date: Tue, 6 Apr 2004 18:13:27 +0200 [thread overview]
Message-ID: <16498.55079.113850.814310@localhost.localdomain> (raw)
In-Reply-To: <16498.53673.93666.636797@localhost.localdomain>
hanwen@xs4all.nl writes:
>
> after bugfix:
>
> byrd:~/usr/src/lilypond$ guile test.scm
> ( 195)( 182)
>
> there is still something broken in this function. For reasons beyond
> my comprehension, the SCM_VALIDATE_SUBSTRING_SPEC_COPY macro has the
> side effect of assigning to cstart and cend, and doing so wrongly.
>
I retract this. Emacs expands the o with dieresis to two bytes
characters; my bad.
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-04-06 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 15:50 bug in srfi-13 Han-Wen Nienhuys
2004-04-06 16:13 ` Han-Wen Nienhuys [this message]
2004-04-15 0:37 ` Kevin Ryde
2004-04-15 1:10 ` Kevin Ryde
2004-04-18 0:22 ` Kevin Ryde
2004-04-24 22:05 ` Kevin Ryde
2004-04-24 22:58 ` Marius Vollmer
2004-05-11 19:15 ` 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=16498.55079.113850.814310@localhost.localdomain \
--to=hanwen@xs4all.nl \
/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).