From: Kevin Ryde <user42@zip.com.au>
Subject: string-split vs 8-bit chars
Date: Sun, 05 Jun 2005 11:49:10 +1000 [thread overview]
Message-ID: <87zmu5h8tl.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
(length (string-split (string #\a (integer->char 255) #\b)
(integer->char 255)))
=> 1
where I think it should be 2.
* srfi-13.c (scm_string_split): Compare char/char in scan. Mixing an
unsigned int SCM_CHAR and a char string meant an 8-bit char was never
matched.
[-- Attachment #2: srfi-13.c.split.diff --]
[-- Type: text/plain, Size: 255 bytes --]
--- srfi-13.c.~1.13.~ 2005-05-26 09:04:39.000000000 +1000
+++ srfi-13.c 2005-06-05 11:44:55.672651856 +1000
@@ -3224,7 +3224,7 @@
{
long idx, last_idx;
const char * p;
- int ch;
+ char ch;
SCM res = SCM_EOL;
SCM_VALIDATE_STRING (1, str);
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2005-06-05 1:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zmu5h8tl.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).