International Lisp Conference 2009

We can forget about Common Lisp and Clojure and Scheme now: the problem has been solved by Joseph F. Miklojcik III, in his new paper, Phosphorus, The Popular Lisp.

Thanks very much to Allan MacKinnon for directing my attention to this thread on Lambda The Ultimate.

CLtL3 Manifesto

Common lisp has never been a static language.Originally, Common Lisp was "designed as a description of a family of languages"[1]. The Lisp systems at the time were largely incompatible with one another, and were often internally inconsistent, but shared many common features and saw wide use.

Registration Fees:
******************

* Early registration before April 25, 2008: Students EU60, regular EU120.
* Late registration before May 16, 2008: Students EU80, regular EU160.
* Onsite registration: Students EU100, regular EU220.

Registration will include the proceedings, coffee breaks,
the symposium dinner and other amenities.
Accommodation is not included.

Scope and Program Highlights:
*****************************

The purpose of the European Lisp Symposium is to provide a forum for
the discussion of all aspects of the design, implementation and

I have published a new, revised version of http://users.rcn.com/david-moon/PLOT/

Has anyone uploaded any pictures from the conference?

Most of the sessions I attended at ILC2009 were recorded, and I presume the intention is that video will be posted at some point. Has that already happened (and I simply haven't stumbled across the relevant links)?

Regardless, thanks in advance to those working at getting that video out on the nets.

Multicore systems are finally standard consumer equipment. How will Common Lisp adapt?

Many other systems have distributions of common, nonstandard packages. Why not Common Lisp?

====
LAIR
====

I propose that the Lisp community build the Lisp All-Inclusive Repository (LAIR). In a nutshell, it's like CPAN: the place to go to get libraries and such. It's "all-inclusive" in the sense of providing this service for all members of the Lisp family, including Scheme and Dylan and Clojure.

I wrote this after being inspired by the "Clornucopia" idea from Clozure Associates LLC. However, this is my own proposal. I am grateful for Clozure's inspiration, but I'm speaking only for myself.

Quotation
=========

The X3.226 standard for Common Lisp is hopefully not the be-all end-all of what Lisp is. If it were, then Lisp would rightfully be doomed.

Neither ANSI CL, nor PLT Scheme, nor Clojure, nor any variant or implementation of any Lisp language or system, has all the features that a Lisper may yearn for. Non-Lisp languages and systems even less.

Is there a will in the community to collaborate towards a better Lisp? One that would, say, embody the features so well presented by Henry Baker in his speech at ILC 2005?

http://international-lisp-conference.org/2005/speakers.html#henry_baker