[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strings/chars

This page is part of the web mail archives of SRFI 50 from before July 7th, 2015. The new archives for SRFI 50 contain all messages, not just those from before July 7th, 2015.

To: shiro@xxxxxxxx
Subject: Re: Strings/chars
From: Tom Lord <lord@xxxxxxx>
Date: Mon, 22 Dec 2003 14:37:48 -0800 (PST)
Cc: srfi-50@xxxxxxxxxxxxxxxxx
Delivered-to: srfi-50@xxxxxxxxxxxxxxxxx
In-reply-to: <20031222.115128.628193033.shiro@xxxxxxxx> (message from Shiro Kawai on Mon, 22 Dec 2003 11:51:28 -1000 (HST))
References: <opr0lf0hi7w2xcd0@xxxxxxxxxxxxx> <20031222.115128.628193033.shiro@xxxxxxxx>


Wow.   Just generally, the char-type/string-type issues stand 
a good chance of hosing this srfi, at least for implementors that care
about unicode.   That blows.

-t

Follow-Ups:
- Re: Strings/chars
  - From: Michael Sperber
- Re: Strings/chars
  - From: Alex Shinn

References:
- Couple things...
  - From: felix
- Strings/chars
  - From: Shiro Kawai

Prev by Date: Re: character strings versus byte strings
Next by Date: Re: character strings versus byte strings
Previous by thread: Strings/chars
Next by thread: Re: Strings/chars
Index(es):
- Date
- Thread