Re: Reasons to choose CLISP over other free implementations

In article
<15207ed2-0552-4be7-b088-04401690da76@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Slobodan Blazeski <slobodan.blazeski@xxxxxxxxx> wrote:

On Nov 28, 7:56 pm, Javier <javu...@xxxxxxxxx> wrote:
What are actually the reasons to choose CLISP over other free
implementations?

I believe there are some. Compared to SBCL, for example:

- Fast bignum operations.
- Fast CLOS instantiations.
- Much faster compiler speed, which is nice for big projects.
- Better memory management. SBCL (and CMUCL) tends to do not return
unallocated memory and wastes a lot of OS virtual memory.
- Better memory footprint. It just need about 4 Mb of memory at
startup.
- Better debugger. CLISP usually allows you to choose from more
options when an error occurs in the debugger.
- Better internationalization. Most messages are translated into
various languages.

What do you think about? Any more ideas?

- No threads so forget about web development.


Why didn't you tell that Paul Graham years back then?

If he knew that , he would have stopped and not
developed the Viaweb editor - in CLISP.

- Using FFI will turn your application into GPLware.

Slobodan
.

Relevant Pages