Matthew Flatt scripsit:

> FWIW: MzScheme originally supported a larger set of characters, mainly
> because extra bits are available my implementation. The resulting bad
> experience convinced me to define characters in terms of scalar values,
> instead.

Can you give the details of the bad experience?

There is a potential problem that a UTF-16 input may contain an unpaired
surrogate, and then it's not clear what to do with it.  Admittedly that's
out of scope for this SRFI, but it'll have to be tackled eventually, and
if surrogate codepoints don't have a representation, the obvious tactic
will be blocked.

--
John Cowan  xxxxxx@reutershealth.com  www.reutershealth.com  www.ccil.org/~cowan
I come from under the hill, and under the hills and over the hills my paths
led. And through the air. I am he that walks unseen.  I am the clue-finder,
the web-cutter, the stinging fly. I was chosen for the lucky number.  --Bilbo