SBCL Internals The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

The basic criteria are that the introduction of Unicode should be invisible to existing code, and that afterwards only minor changes have to be made simultaneously as Unicode related features get implemented. Whether Unicode support is built in is dependent on the compile time conditional feature :SB-UNICODE.

Types BASE-CHAR, BASE-STRING and SIMPLE-BASE-STRING will remain as they are, and CHARACTER, STRING and SIMPLE-STRING will be changed to consist of one or more 21 bit Unicode characters.

If the program does not specify otherwise, all mapping which must interpret strings as octet arrays will use the identity mapping and complain if Unicode values over 255 are encountered. The mechanism of this specification is still open. Possibilities are extra keyword arguments to OPEN and the like, or then defining a special variable, or several special variables, which govern the transformation process.

Actually OPEN already has the EXTERNAL-FORMAT keyword argument for specifying mappings at read and write time. Support for the :UTF-8 argument is just going in character_branch. The same keyword argument is used for MAKE-FD-STREAM and SOCKET-MAKE-STREAM automatically.

Support for 21-bit characters has been merged as of sbcl-0.8.16.26 (2004-11-02).

This page is linked from: Darwin   Teemu Kalvas  

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively