Re: Reasons to choose CLISP over other free implementations

On 29 Nov, 00:17, Javier <javu...@xxxxxxxxx> wrote:

Some of the things you are discussing here are planned tasks for
future CLISP releases. For example, a JIT (just in time compiler, ala
Java), UFFI port, multithreading

About a year ago I found CLISP and SBCL were more distinct than they
are now. To me SBCL meant "speed" and "big" while CLISP meant
"portable" and "small". Now, with CLISP considering adding threads but
it's image size slowly growing while SBCL is starting to look more
attractive on Windows, the distinctions are becoming less obvious.

Of course, there are still many differences between the various
implementations so the best advice is to become familiar with a few of
them and use the one(s) that suits your project(s).

--
Phil
http://phil.nullable.eu/
.