unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Martin Grabmueller <mgrabmue@cs.tu-berlin.de>,
	guile-devel@gnu.org, haus@lambda.math.uni-magdeburg.de
Subject: Re: [Patch] SRFI-13 string-tokenize is wrong
Date: 06 May 2002 20:54:40 +0200	[thread overview]
Message-ID: <87sn55xg27.fsf@zagadka.ping.de> (raw)
In-Reply-To: <uw57kmqdfn9.fsf@lambda.math.uni-magdeburg.de>

Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De> writes:

> Marius Vollmer <mvo@zagadka.ping.de> writes:
> 
> > Thanks; and sorry for being nitpicky: can we be sure that isgraphic is
> > the same as charset:graphic?
> 
> We can't.  That's why I wrote that TOKEN_SET defaults to "an
> equivalent" of CHAR-SET:GRAPHIC.  

Err, I meant "can we be sure that isgraphic is an equivalent of
charset:graphic?".  I suppose it would be better to use the real
charset:graphic but we would have to import it into C land.  (time
passes.)  I have done this now in unstable, but not in stable.

> The whole internationalization stuff is, of course, broken.

Yeah, true.

> BTW, when I tried to make an example of the described behavior, I
> got a segmentation fault caused by an array being indexed by a
> signed char (on Solaris 2.7 with the Forte compiler):

Yes, we hit on a couple of these already.

> Here is a fix:

Thanks, applied!

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2002-05-06 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 17:35 [Patch] SRFI-13 string-tokenize is wrong Matthias Koeppe
2002-04-24 19:58 ` Marius Vollmer
2002-04-26  8:27   ` Matthias Koeppe
2002-04-26 18:18     ` Marius Vollmer
2002-04-29  9:21       ` Matthias Koeppe
2002-05-06 18:54         ` Marius Vollmer [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=87sn55xg27.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-devel@gnu.org \
    --cc=haus@lambda.math.uni-magdeburg.de \
    --cc=mgrabmue@cs.tu-berlin.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).