<?xml version="1.0" encoding="ISO-8859-1" ?><rss version="2.0"><channel><title>The Common Lisp Directory/CDR</title><link>http://www.cl-user.net/asp/tags/CDR</link><description>The last modified items of the Common Lisp Directory for the tag: CDR</description><language>en-US</language><pubDate>Mon, 03 Jun 2013 00:03:30 GMT</pubDate><lastBuildDate>Mon, 03 Jun 2013 00:03:30 GMT</lastBuildDate><generator>Fractal Concept Web Application Framework</generator><item><title>Armed Bear Common Lisp (Annotated)</title><link>http://www.cl-user.net/asp/impl/ABCL</link><guid isPermaLink="false">11745</guid><pubDate>Wed, 06 Mar 2013 13:42:39 GMT</pubDate><description>Armed Bear Common Lisp (ABCL) is an implementation of ANSI Common Lisp that runs in a Java virtual machine.</description></item><item><title>CDR 3: Revisiting CONCATENATE-SEQUENCE (Added)</title><link>http://www.cl-user.net/asp/web-sites/CDR3</link><guid isPermaLink="false">14544</guid><pubDate>Wed, 01 Nov 2006 15:19:33 GMT</pubDate><description>While doing work to support user-extensible sequences, it was discovered that the ANSI CL standard forbids integration of certain functions with not only user-extensible sequences but also implementation extensions of sequence. Irrespective of the future of user-extensible sequences, we argue that the restriction on implementations imposed by the wording adopted is too stringent, and propose an alternative.</description></item><item><title>CDR 2: A generic hash table interface specification for Common Lisp (Added)</title><link>http://www.cl-user.net/asp/web-sites/CDR2</link><guid isPermaLink="false">14492</guid><pubDate>Wed, 18 Oct 2006 21:26:36 GMT</pubDate><description>The hash table interface specified in the Common Lisp standard is only guaranteed to work with keys that are considered equal with either of EQ, EQL, EQUAL or EQUALP. It is sometimes useful for an application to have hash tables using keys with different equality predicates.</description></item><item><title>CDR 1: The CLOS Metaobject Protocol (Added)</title><link>http://www.cl-user.net/asp/web-sites/CDR1</link><guid isPermaLink="false">14491</guid><pubDate>Wed, 18 Oct 2006 21:24:45 GMT</pubDate><description>The CLOS Specification describes the standard Programmer Interface for the Common Lisp Object System (CLOS). This document extends that specification by defining a metaobject protocol for CLOS - that is, a description of CLOS itself as an extensible CLOS program. In this description, the fundamental elements of CLOS programs (classes, slot definitions, generic functions, methods, specializers and method combinations) are represented by first-class objects. The behavior of CLOS is provided by these objects, or, more precisely, by methods specialized to the classes of these objects.

Because these objects represent pieces of CLOS programs, and because their behavior provides the behavior of the CLOS language itself, they are considered meta-level objects or metaobjects. The protocol followed by the metaobjects to provide the behavior of CLOS is called the CLOS Metaobject Protocol (MOP).</description></item><item><title>CDR 0: Common Lisp Document Repository (Added)</title><link>http://www.cl-user.net/asp/web-sites/CDR0</link><guid isPermaLink="false">12729</guid><pubDate>Wed, 18 Oct 2006 21:23:00 GMT</pubDate><description>The Common Lisp Document Repository is a repository of documents that are of interest to the Common Lisp community. The most important property of a CDR document is that it will never change: if you refer to it, you can be sure that your reference will always refer to exactly the same document.</description></item><item><title>The Common Lisp Document Repository (Added)</title><link>http://www.cl-user.net/asp/web-sites/CL%20Document%20Repository</link><guid isPermaLink="false">14095</guid><pubDate>Sat, 12 Aug 2006 16:51:38 GMT</pubDate><description>The Common Lisp Document Repository is a repository of documents that are of interest to the Common Lisp community. The most important property of a CDR document is that it will never change: if you refer to it, you can be sure that your reference will always refer to exactly the same document.
</description></item></channel></rss>