Verbose ASD loading

[phoe]

cxml/cxml.asd

Lines 13 to 37 in adb4430

	(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?

[luismbo]

What about signalling some sort of warning?

…

On Sat, Mar 28, 2020, 9:39 PM phoe ***@***.***> wrote: https://github.com/sharplispers/cxml/blob/adb443043305deb090945364084d393a3b9edcfc/cxml.asd#L13-L37 This codeblock contributes to (IMO unnecessarily) verbose Quicklisp loads of cxml, for instance: ; 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? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALFP3XLDSJJZ46CFG7GCLRJZVBNANCNFSM4LVXDBSQ> .

[phoe]

This could be explored. ASDF might treat that warning as a compilation error and fail the loading operations though; maybe it would be better to signal a non-warning condition instead.