On Wed, 2025-06-11 at 09:06 +0200, Peter Eisentraut wrote:
> > CASE: lower/upper/initcap/fold behavior
> > CLASS: char classifications such as [[:punct:]]
> > ORDER: comparisons
> >
> > Internally, at least for the foreseeable future, CASE and CLASS
> > would
> > be the same. They'd just be different markers to record the user's
> > intent.
>
> Under what scenario would they become different, and how would that
> matter in practice?
I can't think of any reason those behaviors should diverge. If nothing
else, the "uppercase" property should be consistent with the results of
case mapping.
However, I have struggled to come up with a single word that includes
both casing behavior and character classification, but excludes
ordering behavior. Such a word would be useful for documentation, too.
I guess "CTYPE" works, but it's too technical and feels libc-specific.
Regards,
Jeff Davis
