ECL and GCL share some common ancestry, but I don't know the whole
story. I believe Camm Maguire had some discussion with the ECL people
about the possibility of merging the two projects, but that the final
decision was to remain autonomous.
I don't think a port to ECL would give us much that we don't already
have with GCL. If someone feels the desire to a port, however, I won't
try to discourage him/her.
--Jim
On Thu, 2003-02-20 at 08:54, Martin RUBEY wrote:
> I just recalled that there is also ecl
> (http://ecls.sourceforge.net/index.html), which seems to have interesting
> features:
>
> ECL stands for Embeddable Common-Lisp. The ECL project is an
> effort to modernize Giusseppe Attardi's ECL environment to produce an
> implementation of the Common-Lisp language which complies to the ANSI
> X3J13 definition of the language.
>
> The current ECL implementation features:
>
> A bytecodes compiler and interpreter.
> A translator to C.
> An interface to foreign functions.
> A dynamic loader.
> The possibility to build standalone executables.
> ^^^^^^^^^^ (wouldn't this be nice?)
> The Common-Lisp Object System (CLOS).
> Conditions and restarts for handling errors.
> Sockets as ordinary streams.
> The Gnu Multiprecision library for fast bignum operations.
> A simple conservative mark & sweep garbage collector.
> The Boehm-Weiser garbage collector.
>
> Since the developers aim at ansi compliance, a port might be not too
> difficult, who knows...
>
> Martin
--
James Amundson <amundson@fnal.gov>