Email list hosting service & mailing list manager

character strings versus byte strings Matthew Flatt (22 Dec 2003 14:16 UTC)
Re: character strings versus byte strings Per Bothner (22 Dec 2003 17:09 UTC)
Re: character strings versus byte strings Matthew Flatt (22 Dec 2003 17:23 UTC)
Re: character strings versus byte strings tb@xxxxxx (22 Dec 2003 20:23 UTC)
(missing)
(missing)
Re: character strings versus byte strings Tom Lord (22 Dec 2003 22:36 UTC)
Re: character strings versus byte strings tb@xxxxxx (22 Dec 2003 22:41 UTC)
Re: character strings versus byte strings Shiro Kawai (22 Dec 2003 23:00 UTC)
Re: character strings versus byte strings Michael Sperber (23 Dec 2003 09:36 UTC)

character strings versus byte strings Matthew Flatt 22 Dec 2003 14:16 UTC

This looks like an excellent start!

Some suggestions toward addressing the character-encoding issue:

 * Change the API to distinguish between byte strings and character
   strings. (I think C code is as likely to need one as the other).

 * Where "char *" is used for strings (e.g., "expected_explanation" for
   a type error), define it to be an ASCII or Latin-1 encoding (I
   prefer the latter).

 * For Scheme characters, pick a specific encoding, probably one of
   UTF-16, UTF-32, UCS-2, or UCS-4 (but I don't know which is the right
   choice).

An additional request:

 * Distinguish between mutable and immutable strings, particularly in
   checking argument types. (C code that intents to mutate an argument,
   for example, should require a mutable one and reject an immutable
   one.)

Matthew