From: Andy Wingo <wingo@pobox.com>
To: Clinton Ebadi <clinton@unknownlamer.org>
Cc: guile-devel@gnu.org
Subject: Re: `regexp-exec' and non-ascii strings
Date: Thu, 17 Mar 2011 18:54:25 +0100 [thread overview]
Message-ID: <m3k4fxzl7y.fsf@unquote.localdomain> (raw)
In-Reply-To: <87k4gcqb5i.fsf@rvannith.home.unknownlamer.org> (Clinton Ebadi's message of "Sun, 06 Mar 2011 14:52:41 -0500")
On Sun 06 Mar 2011 20:52, Clinton Ebadi <clinton@unknownlamer.org> writes:
> While debugging[0] an issue with Bobot++ (poor sneek!) aborting after
> calling scm_regexp_exec on any utf-8 strings I eventually realized
> that... the string was actually single-byte encoded internally. After
> taking that down the wrong path I eventually tested `regexp-exec' with a
> *valid* latin-1 string and that too aborted in `fixup_multibyte_match'.
This was actually due to scm_to_locale_string() not producing a valid
locale string. Having fixed that, I verified that
meta/guile -c '(display (regexp-exec (make-regexp "(.)(.)(.)") (string (integer->char 200) (integer->char 201) (integer->char 202))))'
no longer triggers the abort.
Thanks for the report,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-03-17 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 19:52 `regexp-exec' and non-ascii strings Clinton Ebadi
2011-03-17 17:54 ` Andy Wingo [this message]
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=m3k4fxzl7y.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=clinton@unknownlamer.org \
--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).