Email list hosting service & mailing list manager

the discussion so far Matthew Flatt (16 Jul 2005 12:41 UTC)
(missing)
(missing)
Re: the discussion so far Alex Shinn (20 Jul 2005 02:50 UTC)
Re: the discussion so far Thomas Bushnell BSG (20 Jul 2005 02:56 UTC)
Re: the discussion so far Alex Shinn (20 Jul 2005 03:15 UTC)
Re: the discussion so far Thomas Bushnell BSG (20 Jul 2005 03:24 UTC)
Re: the discussion so far Alex Shinn (20 Jul 2005 03:38 UTC)
Re: the discussion so far Thomas Bushnell BSG (20 Jul 2005 03:49 UTC)
Re: the discussion so far John.Cowan (20 Jul 2005 04:24 UTC)
Re: the discussion so far Thomas Bushnell BSG (20 Jul 2005 04:27 UTC)
Re: the discussion so far John.Cowan (20 Jul 2005 04:58 UTC)
Re: the discussion so far Thomas Bushnell BSG (20 Jul 2005 05:04 UTC)
(missing)
(missing)
Re: the discussion so far bear (20 Jul 2005 02:45 UTC)
Re: the discussion so far John.Cowan (20 Jul 2005 03:56 UTC)
Re: the discussion so far Jorgen Schaefer (16 Jul 2005 13:05 UTC)
Re: the discussion so far Matthew Flatt (16 Jul 2005 13:21 UTC)
Re: the discussion so far Jorgen Schaefer (16 Jul 2005 13:58 UTC)
Re: the discussion so far Thomas Bushnell BSG (17 Jul 2005 02:42 UTC)
Re: the discussion so far Thomas Bushnell BSG (17 Jul 2005 02:57 UTC)
Re: the discussion so far Jorgen Schaefer (17 Jul 2005 03:33 UTC)
Re: the discussion so far bear (16 Jul 2005 18:07 UTC)
Re: the discussion so far John.Cowan (17 Jul 2005 04:49 UTC)
Re: the discussion so far Thomas Bushnell BSG (17 Jul 2005 02:40 UTC)

Re: the discussion so far Thomas Bushnell BSG 20 Jul 2005 04:27 UTC

"John.Cowan" <xxxxxx@reutershealth.com> writes:

> Thomas Bushnell BSG scripsit:
>
>> I want generically-named procedures to do the correct generic thing on
>> the local system.  I want no generically-named procedures mandated by
>> the standard when they cannot be implemented correctly on a
>> fancy/schmancy system.
>
> There is no "correct generic thing".

Sure there is.  A generically named function on a fancy/schmancy
system should do the correct locale-dependent operation when case
mapping is requested.  It should also provide a "neutral" locale which
will implement the locale-independent case mapping from the Unicode
data files.

>> Now if you want, as a system implementor, to continue to implement
>> them, go right ahead.  But *please* don't force every Scheme system,
>> include a fancy/schmancy one, to do so!
>
> Fancy systems are precisely the ones that need both "small, fast, and simple"
> and "large, slow, and complex".  (These are relative terms.)

Yep.  And the exact contours are unknown.  I'm not asking for nobody
doing design; I'm asking for nobody doing design while they are doing
standardization.  As long as the functions do not rigidly require
specific behaviors that are known to cause problems, and are not
misleadingly named, I'm content.