CL Web Server Options. Sunday, October 17, 2004 There was recently a very good discussion on c.l.l. about the different CL-based web server alternatives that are available. The thread highlighted the fact that there are a wealth of options available if you want to use a CL-based web server; however, the number of different alternatives sometimes tends to confuse people as it is not always apparent what the pros and cons of different options are. I'll try to identify the options that are available and where they might be most appropriate in this post. First of all, there are 3 broad categories of CL-based web server packages: "I think it's always dangerous to underestimate how good a system which has had the amount of battle testing that Apache has can be.
I believe that it is always important to choose " horses for courses ". " If you could go back and change anything, would Red Gorilla still be in business today? CLSQL Users' Guide. Lispdoc - common lisp documentation. Common Lisp hyperspec. The Common Lisp HyperSpec The Common Lisp HyperSpec™ is the acclaimed online version of the ANSI Common Lisp Standard, suitable for LispWorks users. The HyperSpec is derived from the official standard with permission from ANSI and NCITS (previously known as X3). It contains the full text of the ANSI standard and ancillary information. The Common Lisp HyperSpec was prepared (1996) and revised (2005) by Kent Pitman.
As Project Editor of X3J13 Kent Pitman managed the completion of the document which became the ANSI Common Lisp Standard. The ANSI Common Lisp standard contains nearly 1100 pages describing nearly a thousand functions and variables in sufficient detail to accommodate hosting of the language on a wide variety of hardware and operating system platforms. While the ANSI document remains the official standard, we think that in practice you'll find the Common Lisp HyperSpec much easier to navigate and use than its paper/PDF alternative. The Common Lisp Standard CLtL2.
Shell script to build an asdf package. Making a small Common Lisp project. I wrote an updated version of this advice in 2010. You can read it here. I sometimes see people say they don't know where to start when they want to write something in Common Lisp. Here's what I do when I get an idea and I want to explore it with Common Lisp. Open a new file in the editor. So, let's say it's a project to extract some info out of Apache combined log files. Add and evaluate defpackage and in-package forms. (defpackage #:stumpgrinder (:use #:cl)) (in-package #:stumpgrinder) I evaluate the defpackage form with C-c C-c, then start writing definitions after the in-package form.
Write the code. Make it (re-)loadable. Projects grow, though, and libraries are handy. (defpackage #:stumpgrinder (:use #:cl #:cl-ppcre)) However, compiling and loading the file directly will result in an error like this: The name "CL-PPCRE" does not designate any package. ; READ failure in COMPILE-FILE: ; READER-ERROR at some position on some stream: ; package "CL-PPCRE" not found Finish it (sort of).