Another approach to fixing the treatment of CHAR/STRING
in R6 might be found (imperfectly) in:
http://srfi.schemers.org/srfi-52/srfi-52.html
And, in general, one thing that might be more widely
agreed upon than either my formal comment or srfi-52
is that there is no non-controversial way to directly
extend CHAR/STRING from R5 into a full-blown
basis for Unicode programming. Both my formal and
srfi-52 have in common that they try to minimize the
demands on CHAR/STRING and open the door for
exploring how best to *really* provide Unicode
support. Both also recognize the need to reflect on source
code, meanwhile.
-t
Received on Tue Mar 20 2007 - 16:47:50 UTC