case mappings Alex Shinn (13 Jul 2005 03:57 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 05:49 UTC)
Re: case mappings Michael Sperber (13 Jul 2005 06:41 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 06:47 UTC)
Re: case mappings Michael Sperber (13 Jul 2005 07:12 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 07:21 UTC)
Re: case mappings bear (13 Jul 2005 17:24 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 19:35 UTC)
Re: case mappings Alex Shinn (13 Jul 2005 07:55 UTC)
Re: case mappings Alex Shinn (13 Jul 2005 07:40 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 19:36 UTC)
Re: case mappings Alex Shinn (14 Jul 2005 02:39 UTC)
Re: case mappings Thomas Bushnell BSG (14 Jul 2005 07:15 UTC)
Re: case mappings Alex Shinn (14 Jul 2005 07:42 UTC)
Re: case mappings Thomas Bushnell BSG (14 Jul 2005 08:07 UTC)
Re: case mappings Alex Shinn (14 Jul 2005 08:24 UTC)
Re: case mappings bear (14 Jul 2005 16:47 UTC)
Re: case mappings Thomas Bushnell BSG (14 Jul 2005 20:29 UTC)
Re: case mappings bear (15 Jul 2005 18:23 UTC)
Re: case mappings Thomas Bushnell BSG (15 Jul 2005 19:52 UTC)
Re: case mappings Matthew Flatt (13 Jul 2005 13:05 UTC)
Re: case mappings Thomas Bushnell BSG (13 Jul 2005 19:39 UTC)
Re: case mappings Alex Shinn (14 Jul 2005 02:31 UTC)

Re: case mappings Thomas Bushnell BSG 13 Jul 2005 19:39 UTC

Matthew Flatt <xxxxxx@cs.utah.edu> writes:

> I appreciate this line of reasoning, and I'm now convinced that SRFI-75
> (and R6RS) should include locale-independent procedures
>
>   string-upcase
>   string-downcase
>   string-titlecase
>
> that use the locale-independent part of SpecialCasing.txt. I'll add
> that to the SRFI, pending further discussion.

Yay!

(Can we have an optional locale argument too?)

> Although I agree that the 1-1 mapping is of limited use, my impression
> and experience is that it's still useful (if, for nothing else,
> interfacing to older code that uses a 1-1 mapping). So, pending further
> discussion, I will leave the character-casing operations in place.

Can we specify exactly what these return in terms of string-*case?

Perhaps char-upcase should return the first character of the result of
string-upcase on a one-character string.

I once did a survey of the code I had written which did case mapping,
and I discovered, to my surprise, that I did not need even *one* case
of char mapping.  In every case where I used char mapping functions,
it was in some kind of loop across a string.  In the years since, I
keep track, and I still haven't found a situation where the char
functions were needed and string functions were not better.

Also, we need string-caseindependent-= or something of the kind.

Thomas