Re: Reasons to choose CLISP over other free implementations

On Nov 28, 9:28 pm, Rainer Joswig <jos...@xxxxxxx> wrote:
In article
<15207ed2-0552-4be7-b088-04401690d...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Slobodan Blazeski <slobodan.blaze...@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?

He might have listen to me, just imagine the lost buzz :)

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

Yes I know about Clisp / Viaweb story. Even today is possible. But
most people prefer threaded implementation.

- Using FFI will turn your application into GPLware.

Slobodan

.

Relevant Pages

  • Re: Deleting a preloaded image from memory
    ... The variable aVar then gets assigned to memory address ABC. ... these types of generalisations about javascript implementations. ... you waffle on about the history of computers as if it was unknown. ...
    (comp.lang.javascript)
  • Re: Pointer validity
    ... Implementations are allowed to do whatever ... impossible to classify a pointer value as stack or non-stack ... >> Pointers to valid memory locations can come from an external ... >> friends, for locating heap corruption, dangling references, etc. ...
    (comp.lang.c)
  • Re: execution time becomes unpredictable?!
    ... > performance and real implementations of memory heaps *really do* ... > do exist Oimplementations of malloc/free (and realloc, ... As far as I know, gcc, ... > because its open source and "Lea" malloc implementation is reasonably ...
    (comp.lang.c)
  • Re: Dealing with naive malloc() implementations
    ... Were there implementations where this strategy (or something ... A "buddy system" malloc ... fragmentation can cause allocation failure when memory is ... but at a PPOE I did a fairly sizeable amount of work ...
    (comp.lang.c)
  • Re: swap() function without tmp
    ... imagine the microchip programming like a PIC. ... Technically, yes, PIC implementations that don't allow the ... > has not enough memory. ... its own optimizations or directly through inline assembly code ...
    (comp.lang.c)