Allegro CL Examples and Utilities

The following applications and programs demonstrate Allegro CL features and non-trivial ways Lisp can be used. Users are free to experiment with and extend these samples as a way to learn more about Lisp and Allegro CL. If you have an example you'd like us to consider adding to our examples list, you can visit http://examples.franz.com/login to create/use an id to upload files. Alternatively, you can send a message to examples@franz.com.

The list below of examples and utilities indexes a code repository for Lisp and Allegro CL programs. These programs are not officially supported by Franz Inc. Franz Inc. may review submissions and may change the list below at any time. There are NO warranties with regard to submissions or to their use.

All code submissions are intended to be free of charge. Submissions found to be shareware or which request a fee will be removed.

The submissions may be licensed. Contact the submission author to clarify any licensing issue. Submitters considering using the Gnu Lesser General Public License ("LGPL") may wish to look at the LLGPL , the Lisp Lesser GNU Public License . The LLGPL consists of a preamble, developed specifically for Lisp applications, and the LGPL . Please note that when these two conflict, the preamble takes precedence.

Except as noted, each example below is available in source form distributed as a gzipped tar file. Your browser should initiate a download of the file by clicking on the file's name in the entry's File column below. Windows users can use WinZip to recover files from this type of archive. If the text files in a gzipped tar file are stored using the Unix newline convention (i.e., each line ending with ASCII linefeed), then WinZip's default behavior is to convert such files to using the DOS/Windows newline convention when the archive is being unpacked.

If you are having trouble getting an example to work as described, and you are using an Allegro CL version specified in that example's release notes, please try contacting the program's author directly. If the author is noted as being with Franz Inc., then please send a description of the problem to bugs@franz.com.