Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!mcvax!ukc!stc!ist!agc
From: agc@ist.UUCP (Alistair G. Crooks)
Newsgroups: comp.std.internat
Subject: Re: International Collating Sequence
Message-ID: <1483@ist.UUCP>
Date: Fri, 9-Oct-87 11:21:46 EDT
Article-I.D.: ist.1483
Posted: Fri Oct  9 11:21:46 1987
Date-Received: Mon, 12-Oct-87 22:35:13 EDT
References: <2706@sol.ARPA> <29640@sun.uucp> <363@zuring.cwi.nl>
Organization: Imperial Software Technology, London
Lines: 25
Summary: Another way around this...

In article <363@zuring.cwi.nl>, aeb@cwi.nl (Andries Brouwer) writes:
> In article <29640@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
> >An international collating sequence could certainly be cooked up,
> >but in practice who (other than programmers) would want it?
> 
> [...bibliographic journal example deleted...]
> Thus, one has to define some "international collating sequence"
> in such a situation. Does G\*:odel come before or after Godsil?
>       Andries Brouwer -- CWI, Amsterdam -- uunet!mcvax!aeb -- aeb@cwi.nl

With all these thoughts about each separate language's character-sorting
properties, and all the talk in comp.arch on shared libraries (thankfully
dying out now), led me to thinking:

   Why not strip the string routines from libc into a shared library,
   that can be dynamically linked at run time? Or even just strcmp()
   and strncmp()?

This would mean manufacturers would have to write these routines once for
each language. Yes, I know that not everyone has shared libraries (yet),
but in a few months or years time?

Comments, ideas, anyone?

Alistair G. Crooks (agc@ist.co.uk or ...!mcvax!ist!agc)