A 1.0.1 bug fix release for ThinLisp has just been made available. This release fixes some issues when running the ThinLisp Lisp to C translator within CMU Common Lisp as a host environment. At this point the translator has been tested in CLISP, CMU Lisp, Allegro, and MCL. Users have reported trying it in SBCL, and there are edits here that will hopefully resolve issues within that implementation.... read more
I wanted to post a progress report on what I've been working on for the next release of ThinLisp.
Since the release of ThinLisp 1.0 I've been working on pthreads support and lexical closure support. Most of the runtime data structures for pthreads are complete, but to provide the interfaces for pthreads that I want (namely progn-parallel and progn-parallel-race) I need to have lexical closures.
Lexical closures are a glaring lack in ThinLisp today, though I've some reservations about including them. Inadvertent consing of lexical closures is a common performance coding slip-up. Many of the locations where lexical closures are used are where they are passed to mapping functions. In order to ameliorate the lack of lexical closures, most built in mapping functions are implemented as macros. Then, if the function to be mapped is a lambda expresssion, the funcall of that lambda expression will be optimized out into a LET form. ... read more
We're proud to announce the version 1.0 release of ThinLisp, a Lisp to C translator for delivering commercial quality, Lisp-based applications. It implements a subset of Common Lisp with
extensions. ThinLisp itself is written in Common Lisp, and so must run on top of an underlying Common Lisp implementation such as CLISP, Allegro, MCL, or CMU Lisp. The C code resulting from a translation can then be independently compiled to
produce a small, efficient executable image.... read more
In our continuing effort to support ThinLisp on as many Lisp implementations as possible, we've ported the translator to CLISP. It compiles and runs cleanly in CLISP 2.26, which was itself released only a few days ago. This recent release of CLISP fixes many issues that previously prevented a port of ThinLisp, and so only this version or later should be used.
We are migrating the cvs and sources into sourceforge, no ETA at the current time.