Date: Tue, 13 Aug 1996 17:54:00 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) <ache@nagual.ru> To: bde@zeta.org.au (Bruce Evans) Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-lib@freefall.freebsd.org Subject: Re: cvs commit: src/lib/libc/locale collcmp.c Message-ID: <199608131354.RAA01737@nagual.ru> In-Reply-To: <199608131101.VAA10191@godzilla.zeta.org.au> from "Bruce Evans" at "Aug 13, 96 09:01:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > Modified: lib/libc/locale collcmp.c > > Log: > > There is so many places where range comparation (using collate) > > needed (much more than I think initially), so I forced to add > > new user-visible non-standard function to libc. > > This is probably OK for applications, but please try not to introduce > more nonstandard namespace-polluting names that are referenced from > separate libraries (collate_range_cmp is referenced from libgnuregex). I don't plan to introduce more, one function is enough. It needed for _all_ cases where [a-z]-type national letters ranges used, including gnuregex, of course. The reason is simple: letters in the top half of code table usually not sorted alphabetically. Using exact code table layout ranges make additional portablity troubles, i.e. I can covert shell script which use [<Russian A>-<Russian YA>] range to another Russian code table easily, but all non-alphabetical ranges (exact layout ranges f.e.) needs additional porter attention. POSIX 1003.2 also says that collate can be used in [a-z]-type ranges. -- Andrey A. Chernov <ache@nagual.ru> http://www.nagual.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608131354.RAA01737>