Analysis of the state of different Windows LISP implementations.

Team Members

Volunteer today
...or just go ahead and research a LISP and post your findings

Resources

The goal here is to get a comprehensive list of Windows compatible implementations with some useful info about each; pros/cons etc. Eventually this should probably further get digested into some nice comparison charts.

Peter Seibel posted a good summary of options.
Transferring some of that info here would be a good start for this page.

CLiki has an implementation summary page

The ALU Wiki has an implementation page

What about GCL? - No swank backend (for slime) partial implementation. Default builds not ANSI compliant.

Cygwin and clisp is an option. But GNU Emacs has problems in Cygwin, so Cygwin/X is a better option.

But clisp doesn't need cygwin at all. It builds using mingw quite good and compiles to native windows binaries.

Sourceforge currently offers pre-compiled Windows versions of clisp; both with GNU readline & gettext and without it. License-wise, they both seem to be under the GNU, though the version without readline and gettext is about half the size of the other.

Commercial versions with free trials:

• LispWorks - 4 hour reset
• Allegro CL - 60 days (automatically renewable)
• Corman Lisp - 30 days (after which a periodic nag screen appears (if you use the IDE))