[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Case insensitivity ad nauseum
From: |
Ken Clement |
Subject: |
Re: Case insensitivity ad nauseum |
Date: |
18 Nov 2003 10:59:10 -0800 |
A few more comments about case sensitivity in identifiers...
Case sensitivity is a unique issue with Roman characters. The issue
does not come up with Chinese although I suppose there is some
similarity with Japanese Kana (Hiragana v. Katakana). Making
identifiers case-insensitive adds special logic that deals uniquely
with the Roman characters in a manner different than any other unicode
character.
It makes more sense to define orderings and comparisions of a
character set separately from the character itself. This not only
permits character strings to sort according to something other that
its binary representation which is practically required for
internationalizaiton. It consequently permits comparison to be done
on something other than a byte-by-byte binary basis. This makes the
issue something of a user choice as the system can be configured with
the desired sort/comparison sequence. Microsoft SQL Server takes this
approach.
- Re: Case insensitivity ad nauseum, (continued)
- Re: Case insensitivity ad nauseum, Derek Robert Price, 2003/11/05
- Re: Case insensitivity ad nauseum, Donald Sharp, 2003/11/05
- Re: Case insensitivity ad nauseum, Kevin Layer, 2003/11/05
- Re: Case insensitivity ad nauseum, Larry Jones, 2003/11/05
- RE: Case insensitivity ad nauseum, Greg A. Woods, 2003/11/06
- Message not available
- RE: Case insensitivity ad nauseum, Jim.Hyslop, 2003/11/05
- RE: Case insensitivity ad nauseum, Jim.Hyslop, 2003/11/05
- RE: Case insensitivity ad nauseum, Jim.Hyslop, 2003/11/05
- RE: Case insensitivity ad nauseum, Jim.Hyslop, 2003/11/06
- RE: Case insensitivity ad nauseum, Jim.Hyslop, 2003/11/06
- Re: Case insensitivity ad nauseum, Paul Edwards, 2003/11/07