constant-time access to variable-width encodings
Per Bothner
(13 Jul 2005 18:13 UTC)
|
Re: constant-time access to variable-width encodings
Ray Blaak
(13 Jul 2005 18:48 UTC)
|
Re: constant-time access to variable-width encodings
Shiro Kawai
(13 Jul 2005 20:16 UTC)
|
Re: constant-time access to variable-width encodings
Per Bothner
(13 Jul 2005 20:36 UTC)
|
Re: constant-time access to variable-width encodings
Shiro Kawai
(13 Jul 2005 23:07 UTC)
|
Re: constant-time access to variable-width encodings
bear
(14 Jul 2005 00:23 UTC)
|
Re: constant-time access to variable-width encodings
Per Bothner
(14 Jul 2005 00:39 UTC)
|
Re: constant-time access to variable-width encodings
bear
(14 Jul 2005 01:52 UTC)
|
Re: constant-time access to variable-width encodings Thomas Bushnell BSG (14 Jul 2005 07:18 UTC)
|
Re: constant-time access to variable-width encodings
Thomas Bushnell BSG
(14 Jul 2005 07:16 UTC)
|
Re: constant-time access to variable-width encodings Thomas Bushnell BSG 14 Jul 2005 07:18 UTC
Per Bothner <xxxxxx@bothner.com> writes: > Huh? A glyph depends on a specific font. No way can we define Scheme > characters in terms of glyphs. Not in Unicode speak. > Do you mean a (canonicalized) composite (combining) sequence? One > problem is you can't practially map one of those to a fixed-length > integer value, so we have to give up char->integer and > integer->char. Says who? char->integer does not say anything about a "fixed-length integer value". You sound like a C programmer! Scheme doesn't have a concept of "fixed-length integer value" anyhow. > Nonetheless, Java defines the Strings equals routine in terms of code > point equality, and Java programmers manage to get useful work done. Yes, by failing to implement Unicode correctly. If you don't care about correct Unicode implementation, fine, but please don't create a messy standard that *prevents* those who do care from doing it right.