[Openmcl-devel] Unicode in OpenMCL
keke at gol.com
Thu Jun 24 01:27:33 EDT 2004
I agree that UTF-32 character is the best choice.
It is the only choice considering that Lisp has a character
Gary Byers wrote:
> We obviously need to be able to do I/O to and from other encodings
> (and to be able to use various encodings with the FFI), and it's
> fairly clear that we'd want to have lisp objects of type
> UTF-8-ENCODED-STRING (etc.)
The need for UTF-8-ENCODED-STRING is not clear to me.
Is it for FFI?
> It's equally clear (to me, at least) that
> we don't want things like UTF-8-ENCODED string to be of type STRING
> (e.g., we may want to support things like ENCODED-SCHAR or
> ENCODED-STRING-LENGTH, but don't want things like SCHAR and LENGTH to
> have to worry about them. I'm not sure that an ENCODED-STRING should
> be mutable; at the very least, it should be recognized that if (SETF
> (ENCODED-SCHAR s i) c) exists, it might not be a simple operation.)
More information about the Openmcl-devel