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.
At Mon, 22 Dec 2003 14:37:48 -0800 (PST), Tom Lord wrote: > > 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. I don't think Unicode is the problem. Shiro's proposal is well thought out, handles encoding simply, and is based on real working practice in Gauche. The main complication is that Scheme strings don't necessarily have anything to do with C strings. Shared substrings, in fact, are not C strings as already acknowledged by the API and strings as lists or Boehm cords aren't even consecutive memory references. Handle these issues and the only thing left for Unicode is to specify the default encoding (and an advanced SRFI could specify fetching w/ alternate encodings for efficiency). -- Alex