[armedbear-devel] lisp source files encoding
Hello. Starting from ASDF 2.21 it is possible to specify lisp source files encoding in defsystem (see asdf manual: http://common-lisp.net/project/asdf/asdf.html#Miscellaneous-additional-funct...). ABCL now comes with ASDF 2.25. But still encoding specification doesn't work on ABCL. See this log for example: https://cl-test-grid.appspot.com/blob?key=564037 The system being compiled specifies :encoding :ut8 in its defsystem, and we saw the encoding specification working - it fixed compiilation on SBCL. But on ABCL it still fails. Does anyone have idea why so? Is it because of the way ASDF is integrated into ABCL? Or ABCL just doesn't support utf-8 lisp files at all? Best regards, - Anton
On 10/21/12 4:06 PM, Anton Vodonosov wrote:
Hello.
Starting from ASDF 2.21 it is possible to specify lisp source files encoding in defsystem (see asdf manual: http://common-lisp.net/project/asdf/asdf.html#Miscellaneous-additional-funct...).
ABCL now comes with ASDF 2.25.
But still encoding specification doesn't work on ABCL. See this log for example: https://cl-test-grid.appspot.com/blob?key=564037
The system being compiled specifies :encoding :ut8 in its defsystem, and we saw the encoding specification working - it fixed compiilation on SBCL.
But on ABCL it still fails.
Does anyone have idea why so? Is it because of the way ASDF is integrated into ABCL? Or ABCL just doesn't support utf-8 lisp files at all?
We shouldn't have a problem loading UTF-8 source files at all. Filed as ticket [#255][] to track resolution. [#255]: http://trac.common-lisp.net/armedbear/ticket/255 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."
On 10/21/12 6:57 PM, Mark Evenson wrote: […]
Filed as ticket [#255][] to track resolution.
COMPILE-FILE was ignoring its argument, which should be fixed in [r14212][]. [r14212]: http://trac.common-lisp.net/armedbear/changeset/14212 The Quicklisp system your example, com.informatimago.common-lisp.diagram, still fails to compile hanging in some sort of loop (bad!) but past the UTF-8 loading issue. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."
Mark Evenson <evenson@panix.com> writes:
On 10/21/12 6:57 PM, Mark Evenson wrote: […]
Filed as ticket [#255][] to track resolution.
COMPILE-FILE was ignoring its argument, which should be fixed in [r14212][].
[r14212]: http://trac.common-lisp.net/armedbear/changeset/14212
The Quicklisp system your example, com.informatimago.common-lisp.diagram, still fails to compile hanging in some sort of loop (bad!) but past the UTF-8 loading issue.
Thank you. I cannot run abcl for now (I couldn't install Oracle JDK lately), but I'll do it next month and see what's happening with com.informatimago. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.
No need for you to run ABCL, as it will soon be tested by cl-test-grid and results will be published. You can just monitor your library status on http://common-lisp.net/project/cl-test-grid/library/com.informatimago.html Best regards, - Anton
participants (3)
-
Anton Vodonosov -
Mark Evenson -
Pascal J. Bourguignon