|Version 117 (modified by rme, 4 years ago) (diff)|
About Clozure CL
Clozure CL is a free Common Lisp implementation that runs on the following platforms:
- Mac OS X 10.5 and later (ppc32, ppc64, x86, x86-64)
- Linux (ppc32, ppc64, x86, x86-64, armv7l)
- FreeBSD 6.x and later (x86, x86-64)
- Solaris (x86, x86-64)
- Microsoft Windows XP and later (x86, x86-64)
Some distinguishing features of the implementation include fast compilation speed, native OS threads, a precise, generational, compacting garbage collector, and a convenient foreign-function interface.
Clozure CL used to be called OpenMCL. It is also sometimes called CCL. You will see the three names being used interchangeably.
See SystemRequirements for more details on hardware and software requirements.
Getting Clozure CL
The most recent released version of Clozure CL is version 1.6.
Please see http://ccl.clozure.com/download.html for information on how to download it.
After installing CCL, read about getting updates and bug fixes.
Some users may wish to run the development version of Clozure CL, which is often called the "trunk".
To get the trunk version of Clozure CL for Darwin/x86, you'd type (where the $ is the shell prompt):
$ svn co http://svn.clozure.com/publicsvn/openmcl/trunk/darwinx86/ccl
To get a version for a different platform, change the darwinx86 to linuxx86, freebsdx86, solarisx86, windows, darwinppc, linuxppc, or linuxarm.
If you choose to run the trunk, please read about tracking the development version.
The Clozure CL manual is available as a single web page at http://ccl.clozure.com/ccl-documentation.html or as multiple pages at http://ccl.clozure.com/manual/. As of Clozure CL 1.2, the DocBook sources for the manual are included with the distribution.
We have started to collect a list of FrequentlyAskedQuestions.
There are two CCL-related mailing lists hosted at clozure.com. Click on a list's link to subscribe or to view archived messages.
- firstname.lastname@example.org is for general and technical discussion of Clozure CL.
- email@example.com is a low-volume list for release announcements.
Clozure Associates provides commercial support and consulting services for Clozure CL as well as other Common Lisp implementations. These services can range from helping you debug your software to adding extensions to CCL, to providing several full time Lisp programmers to help you build your application. Please contact us at business@… for more information.
- Getting Around in CCL - quick tips for working with CCL's toplevel.
- Installing Slime -- Install Slime and configure it for use with CCL.
- CCL Hints -- Tips and Tricks from Clozure CL Experts (and wanna-be's).
- The Inspector -- How to use CCL's Inspector.
- Building Large Projects -- How to construct software consisting of multiple Lisp source files.
- Tracking CCL changes -- How to keep up with the latest changes.
- Tracking the development version -- There are reasons why the trunk is called the "bleeding edge".
- Windows Notes -- some notes on installing and running Clozure CL on Windows
- Web Development? - Easily install Hunchentoot
Contributing to CCL
- Committing your own changes into SVN -- Let us know if you want write access to the SVN repository.
- Clozure CL FFI -- Working with external libraries
- Cocoa Bridge -- Create Rich User Interfaces with the Cocoa Bridge
- Easy GUI -- Create slightly less Rich Interfaces with Easy GUI
- Apple's Currency Converter in Lisp -- Build Apple's Currency Converter tutorial example in Lisp
- Clozure CL Internals -- Learn the magic behind the scenes
- Declare Optimize -- What do optimization declarations do and how is this implemented
- Threads and Setf -- In what ways is assignment atomic?
- How Fast Are We compared to other Lisps?
- IDE Internals and architecture -- How the CCL IDE works
- IDE (Hemlock) Command Implementor's Manual -- detailed documentation on CCL's editor
- IDE Doc Under Development -- future IDE manual sections, work in progress.
- Running CCL Under GDB
- Vector Streams -- CCL's bivalent byte vector streams
- Memory Utilities -- Find out what kinds of objects are filling up your memory
- Code Coverage -- Find out which parts of your source are being invoked
- Building the FFI translator - Build the "ffigen" interface translator from source.