Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Update of /cvsroot/sbcl/sbcl
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2406
"It's all part of the learning experience"
Preparation for widening CHARACTER.
... rewrite SYMBOLICATE to avoid needing the type system early;
instead essentially provide a specialized
... slightly frob the CONCATENATE and REPLACE transforms
(removing the REPLACE one completely for character
strings, until the widening occurs).
RCS file: /cvsroot/sbcl/sbcl/Attic/TODO.character,v
retrieving revision 220.127.116.11
retrieving revision 18.104.22.168
diff -u -d -r22.214.171.124 -r126.96.36.199
--- TODO.character 20 Sep 2004 13:01:22 -0000 188.8.131.52
+++ TODO.character 20 Sep 2004 16:04:23 -0000 184.108.40.206
@@ -122,6 +122,15 @@
compiler such as CONVERT-MEMBER-TYPE, TWO-ARG-DERIVE-TYPE
+** increase CHAR-CODE-LIMIT to something larger than 256. (Rationale:
+support people other than simply those living in non-Eurozone Western
+Europe or the United States of America.) This requires at minimum
+adjusting the dumper/fop code and the low-level memory accessors.
+ -- in progress for x86:
+ >> rewrote SYMBOLICATE to avoid needing the type system (or a
+ transformed to low-level bit-bashing CONCATENATE) early in
** implement an SB-ALIEN:UTF8-STRING parallel to SB-ALIEN:C-STRING.
(Rationale: for calling out to Pango or similar. Actually, a valid
use might be in Unix libc/kernel functions: at least under Linux, I
@@ -130,11 +139,6 @@
make the #.(coerce "foo" 'base-string) in the filesystem / SB-UNIX
layer go away.
-** increase CHAR-CODE-LIMIT to something larger than 256. (Rationale:
-support people other than simply those living in non-Eurozone Western
-Europe or the United States of America.) This requires at minimum
-adjusting the dumper/fop code and the low-level memory accessors.
** possibly retain a CHAR-CODE-LIMIT = 256 build option, with
character point encoding dependent on locale. This requires
implementing, at a minimum, latin-X eternal formats, so that files
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.1806.2.24
retrieving revision 1.1806.2.25
diff -u -d -r1.1806.2.24 -r1.1806.2.25
--- version.lisp-expr 20 Sep 2004 13:01:22 -0000 1.1806.2.24
+++ version.lisp-expr 20 Sep 2004 16:04:29 -0000 1.1806.2.25
@@ -17,4 +17,4 @@
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)