|
(progn |
|
(format t "~&;;; Checking for wide character support...") |
|
(force-output) |
|
(flet ((test (code) |
|
(and (< code char-code-limit) (code-char code)))) |
|
(cond |
|
((not (test 50000)) |
|
(format t " no, reverting to octet strings.~%") |
|
#+rune-is-character |
|
(error "conflicting unicode configuration. Please recompile.") |
|
(pushnew :rune-is-integer *features*)) |
|
((test 70000) |
|
(when (test #xD800) |
|
(format t " WARNING: Lisp implementation doesn't use UTF-16, ~ |
|
but accepts surrogate code points.~%")) |
|
(format t " yes, using code points.~%") |
|
#+(or rune-is-integer rune-is-utf-16) |
|
(error "conflicting unicode configuration. Please recompile.") |
|
(pushnew :rune-is-character *features*)) |
|
(t |
|
(format t " yes, using UTF-16.~%") |
|
#+(or rune-is-integer (and rune-is-character (not rune-is-utf-16))) |
|
(error "conflicting unicode configuration. Please recompile.") |
|
(pushnew :rune-is-utf-16 *features*) |
|
(pushnew :rune-is-character *features*))))) |
This codeblock contributes to (IMO unnecessarily) verbose Quicklisp loads of cxml, for instance:
To load "foo-system":
Load 1 ASDF system:
foo-system
; Loading "foo-system"
.
;;; Checking for wide character support... WARNING: Lisp implementation doesn't use UTF-16, but accepts surrogate code points.
yes, using code points.
..
;;; Checking for wide character support... WARNING: Lisp implementation doesn't use UTF-16, but accepts surrogate code points.
yes, using code points.
;;; Building Closure with CHARACTER RUNES
...............................................
...................Is it possible/desired to remove the FORMAT calls altogether?
