Projects tagged ‘common_lisp’

Steel Bank Common Lisp, aka SBCL, is an open source compiler and runtime system for ANSI Common Lisp. It provides an interactive environment including an integrated native compiler, a debugger, and many extensions.

SLIME is a new Emacs mode for Common Lisp development. Inspired by existing systems such Emacs Lisp and ILISP, we are working to create a fresh new environment for hacking Common Lisp in. SLIME ... [More] extends Emacs with new support for interactive programming in Common Lisp. The features are centered around slime-mode, an Emacs minor-mode that complements the standard lisp-mode. While lisp-mode supports editing Lisp source files, slime-mode adds support for interacting with a running Common Lisp process for compilation, debugging, documentation lookup, and so on. The slime-mode programming environment follows the example of Emacs's native Emacs Lisp environment. We have also included good ideas from similar systems (such as ILISP) and some new ideas of our own. SLIME is constructed from two parts: a user-interface written in Emacs Lisp, and a supporting server program written in Common Lisp. The two sides are connected together with a socket and communicate using an RPC-like protocol. The Lisp server is primarily written in portable Common Lisp. The required implementation-specific functionality is specified by a well-defined interface and implemented separately for each Lisp implementation. This makes SLIME readily portable. [Less]

GNU CLISP is an ANSI Common Lisp implementation with an interpreter, compiler, debugger, object system (CLOS, MOP), sockets, fast bignums, arbitrary precision floats, and foreign language interface which runs on most UNIXes and Win32.

Maxima is a Common Lisp implementation of MIT's Macsyma system for computer based algebra. It features plotting over the network via netmath, computations over the network, extensive testing on a ... [More] large array of problems, a source level debugger for maxima code, ease of extension in fundamentally new ways, access to Common Lisp and portability to many systems. [Less]

Multi-platform SQL interface for Common Lisp, with bindings to many Lisp implementations and many databases

ABCL is an implementation of Common Lisp running in the JVM: it can run in the same JVM as your Java code, allowing full mixture of Lisp and Java code. With support for JSR-223, you easily extend any ... [More] JSR-223 compatible application with Lisp as a macro language. Based on Java technology, ABCL benefits from the write-once-run-everywhere that Java programs get, such as running on Google App Engine. [Less]

a high-performance, free Common Lisp implementation which runs on most major Unix platforms. It mainly conforms to the ANSI Common Lisp standard.

Elephant is a persistent object protocol and database for Common Lisp. The persistent protocol component of elephant overrides class creation and standard slot accesses using the Meta Object Protocol ... [More] (MOP) to render slot values persistent. Database functionality includes the ability to persistently index and retrieve ordered sets of class instances and ordinary lisp values. Values are stored persistently on disk by one or more 'data stores', which currently consist of Berkeley DB and SQL servers via CL-SQL. A pure-lisp data store is under development. Elephant inherits the ACID properties of these stores, and by design is transactional, multi-threaded, and in the case of Berkeley DB, process safe. [Less]

Autobench is a tool that automatically builds and benchmarks Common Lisp implementations (but can be used to autobuild & benchmark other things as well). It is being used to compile the historical ... [More] benchmark graphs for SBCL, CMUCL, and CLISP, also known as "Boinkmarks". [Less]

ASDF dependency grovel helps you maintain a Common Lisp system that is both easy to develop and speedy to recompile - think of it as a "make depend" for Lisp. It allows you to keep your system ... [More] definition in a serial (or condensed) shape, and figures out the dependencies between the system's components itself. This helps you or your users to incrementally compile the system when files change, without going insane from maintaining tens of compile/load-time dependencies for every file in the system. [Less]