History of LISP

“The goal of this project is to collect, preserve, and present source code, design documents, and other materials concerning the original LISP I/1.5 system, and as many of its follow-ons as possible. LISP was one of the earliest high-level programming languages and introduced many ideas such as garbage collection, recursive functions, symbolic expressions, and dynamic type-checking; it is still in use. This is a project of the Computer History Museum‘s Software Preservation Group. The editor appreciates comments, suggestions, and donations of additional materials…”

http://www.softwarepreservation.org/projects/LISP/

State of the Common Lisp Ecosystem, 2015

“This is a description of the Common Lisp ecosystem, as of August 2015, from the perspective of a user and contributor.

The purpose of this article is both to give an overview of the ecosystem, and to help drive consolidation in each domain.

Each application domain has recommendations for consolidating that part of the ecosystem, and pointers for interesting future work…”

http://eudoxia.me/article/common-lisp-sotu-2015/

Debugging Lisp

Debugging Lisp Part 1: Recompilation

This post is the start of a series on how to debug Common Lisp code, specifically with Emacs, Slime, and SBCL. If you do not understand Common Lisp, you should still be able to follow along and recognize just how powerful the facilities provided by the Common Lisp debugger are. Nathan Marz asked me to write these posts since he thought many of the tools for debugging Common Lisp were pretty cool…

http://malisper.me/2015/07/07/debugging-lisp-part-1-recompilation/

Debugging Lisp Part 2: Inspecting

In this post I am going to discuss another tool used for debugging Common Lisp – the Slime Inspector. The Slime inspector makes it possible to manipulate objects directly from the repl. You can do many different many different things with it, including clicking on objects to look at their contents and being able to copy and past objects in order to reuse them in future function calls…

http://malisper.me/2015/07/14/debugging-lisp-part-2-inspecting/

Debugging Lisp Part 3: Redefining Classes

The Common Lisp Object System (CLOS) is pretty powerful. It gives you multiple inheritance, multiple dispatch, and many different ways to extend the behavior of methods. Underneath, most implementations use the Metaobject Protocol (MOP), a way of defining CLOS in terms of itself. As part of the MOP, classes are implemented as objects with several instance variables. Among those are variables that hold the class’s name, its superclasses, and a list of the class’s own instance variables. If you don’t believe me, take the point class from the previous post:…

http://malisper.me/2015/07/22/debugging-lisp-part-3-redefining-classes/

Debugging Lisp Part 4: Restarts

Many languages provide error handling as two distinct parts, throw and catch. Throw is the part that detects something has gone wrong and in some way signals that an error has occurred. In the process, throw creates an exception object which contains information about the problem. The other part, catch, takes the exception object signaled by throw and attempts to recover from the error…

http://malisper.me/2015/08/05/debugging-lisp-part-4-restarts/

How to process input and output streams in Steel Bank Common Lisp?

“I’m trying to figure out how to use the output stream of one program I start with RUN-PROGRAM so it can be used as the input of another program started with RUN-PROGRAM (i.e., the moral and perhaps literal equivalent of piping). I’ve tried using a number of combinations of the :INPUT, :OUTPUT and :WAIT keyword arguments, but nothing I’ve hit upon has been productive so far. Any tips would be helpful; for example, how would I go about doing something like ls | grep lisp from the shell?…”

http://stackoverflow.com/questions/2353353/how-to-process-input-and-output-streams-in-steel-bank-common-lisp