Re: public bashing of clisp

[Bruno H. <br...@cl...>]

Hello William,

>   CLISP maintainers don't test whether their releases
>   contain bugs which break the SBCL build process.

>   CLISP: has been made to work in the past, but didn't work
>   as of May 2004.

Either of these is accurate; thanks for being nice from now on :-)

>   CLISP: pointedly demonstrates that our so-called "portable ANSI
>     CL build process" is fundamentally less portable than we had
>     thought, um; we're working on it.

It would be too early to conclude this way, I think, before debugging it in
depth. And at least for me, before being able to debug it, I'd need to have a
tool that compares a .lisp-obj built by CMUCL or OpenMCL with a .lisp-obj
built by CLISP (similar to what 'objdump' can produce: data and disassembly).
Christophe told me such a tool does not yet exist.

Greetings,

Bruno