sharplispers / cxml

Closure XML - A Common Lisp XML Parser
http://common-lisp.net/project/cxml/
Other
12 stars 5 forks source link

Verbose ASD loading #7

Open phoe opened 4 years ago

phoe commented 4 years ago

https://github.com/sharplispers/cxml/blob/adb443043305deb090945364084d393a3b9edcfc/cxml.asd#L13-L37

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 commented 4 years ago

What about signalling some sort of warning?

On Sat, Mar 28, 2020, 9:39 PM phoe notifications@github.com 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 https://github.com/sharplispers/cxml/issues/7, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALFP3XLDSJJZ46CFG7GCLRJZVBNANCNFSM4LVXDBSQ .

phoe commented 4 years ago

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.