Re: Reasons to choose CLISP over other free implementations



On 28 nov, 20:45, "John Thingstad" <jpth...@xxxxxxxxx> wrote:

To slow with byte interpretation. I might as well use python..

Python is not Lisp: doesn't have closures, macros and CLOS. And it is
still much slower than CLISP. So I don't get your point.

Note that CLISP, even being bytecode compiled, is faster than SBCL in
some areas (and slower in others, of course).
.



Relevant Pages