[cl-faq] [lispfaq commit] r14 - trunk
codesite-noreply@google.com
codesite-noreply at google.com
Thu Mar 8 13:38:33 CST 2007
Author: peter.seibel
Date: Thu Mar 8 11:37:55 2007
New Revision: 14
Modified:
trunk/faq.txt
trunk/lispfaq.txt
Log:
Moving implementation lists from lispfaq to faq.
Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt (original)
+++ trunk/faq.txt Thu Mar 8 11:37:55 2007
@@ -128,6 +128,108 @@
Oh, and did we mention, the HyperSpec?
+*** Where can I get a free Lisp system?
+
+There are a number of free (in both the "gratis" and the "libre"
+senses) Lisp environments:
+
+\b{\link{\href{http://clisp.cons.org/}\text{CLISP}}}
+
+A lightweight common lisp interpreter and compiler, which compiles to
+bytecode, and runs on Windows, and most flavours of Unix including OS
+X. CLISP is licensed under the GNU GPL.
+
+\b{\link{\href{http://www.cons.org/cmucl/}\text{CMUCL}}}
+
+CMUCL (Carnegie Mellon University Common Lisp) provides an interpreter
+and optimizing, native-code compiler and runs on a few flavours of
+Unix (including x86/FreeBSD, x86/Linux and sparc/Solaris). CMUCL can
+be difficult to compile; it requires itself to build itself, and
+bootstrapping is an issue. CMUCL is mostly public domain software,
+though portions are under an X-like or BSD-like licence.
+
+\b{\link{\href{http://ecls.sourceforge.net/}\text{ECL}}}
+
+ECL (Embeddable Common Lisp) is an implementation of Common Lisp
+running on at least x86, Sparc and PPC architectures, under Linux,
+FreeBSD, Solaris, MacOSX and Windows (using the cygwin environment).
+ECL provides a bytecode compiler and can also compile to C source. ECL
+is licensed under the GNU LGPL.
+
+\b{\link{\href{http://savannah.gnu.org/projects/gcl/}\text{GCL}}}
+
+GCL (GNU Common Lisp) was developed in conjunction with a few large
+programs, most notably the computer algebra system
+\link{\href{http://maxima.sourceforge.net/}\text{Maxima}}. It was
+originally an implementation of the version of Common Lisp described
+in the first edition of \i{Common Lisp the Language} and it's
+developers made few steps toward ANSI compilance. In recent years,
+however, the GCL developers have begun working toward fuller
+compliance with the ANSI standard. GCL is licensed under the GNU LGPL.
+
+\b{\link{\href{http://openmcl.clozure.com/}\text{OpenMCL}}}
+
+OpenMCL is an opensourced Common Lisp implementation derived from MCL
+4.2, and runs on MacOS X and Linux/PowerPC. It includes a bridge to
+the Cocoa framework that allows convenient manipulation of Objective C
+objects in CLOS. OpenMCL is licensed under the GNU LGPL.
+
+\b{\link{\href{http://www.poplog.org/}\text{Poplog}}}
+
+Poplog is an incrementally-compiled runtime that includes a Common
+Lisp implementation, an ML implementation and a Prolog implementation,
+all cohabiting in the same image. It is licensed under an
+XFree86-style license. Poplog CL is not actively maintained.
+
+\b{\link{\href{http://sbcl.sourceforge.net/}\text{SBCL}}}
+
+SBCL (Steel Bank Common Lisp) is a fork of CMUCL aimed at improving
+maintainability by fixing the bootstrapping issues involved in
+recompiling. It can be compiled using any ANSI compliant Common Lisp.
+It runs on many Unix and Unix-like systems (including Mac OS X). SBCL
+is licensed in a similar fashion to CMUCL: mostly in the Public
+Domain, with some BSD-like and MIT-like portions.
+
+*** Where can I buy a commercial Lisp system?
+
+Over time there have been quite a few vendors of commercial Lisp
+systems. The following are the most active:
+
+\b{\link{\href{http://www.franz.com/}\text{Allegro Common Lisp}}}
+
+Franz Inc's Allegro Common Lisp is a fine lisp development environment
+that runs and almost all platforms. See their website for more
+details.
+
+\b{\link{\href{http://www.corman.net/CormanLisp.html}\text{Corman Lisp}}}
+
+Corman Lisp is a compiler for Windows 95/98/2000/ME/NT, with
+integration with the Windows API. It is free for personal use and
+fairly inexpensive compared to other commercial lisps otherwise.
+
+\b{\link{\href{http://www.lispworks.com/products/lispworks.html}\text{LispWorks}}}
+
+LispWorks is the main product of the company of the same name. It is
+available in a variety of editions including a free (as in beer)
+personal edition with a few limitations on its use. Lispworks also
+provides Liquid Common Lisp, a.k.a. LCL, another Common Lisp with a
+slightly different set of extensions above the ANSI specification than
+Lispworks (the Lisp). Unless you are already using LCL, if you are
+going to use a Lispworks (the company) product, you probably want
+Lispworks (the Lisp).
+
+\b{\link{\href{http://www.digitool.com/}\text{MCL}}}
+
+A commercial, implementation of Common Lisp for the Macintosh.
+Digitool has not shown a lot of signs of life lately; their web page
+list of "What's New" was last updated in 2005.
+
+\b{\link{\href{http://www.scieneer.com/}\text{Scieneer Pty Ltd}}}
+
+An implementation of Common Lisp that can take advantage of SMP
+machines. Runs on various Unixes and was originally based on the CMUCL
+code base.
+
*** Do I have to learn Emacs?
Not necessarily. The simplest possible development Lisp environment
Modified: trunk/lispfaq.txt
==============================================================================
--- trunk/lispfaq.txt (original)
+++ trunk/lispfaq.txt Thu Mar 8 11:37:55 2007
@@ -8,25 +8,6 @@
** Possibly useful
-*** What is the Lisp equivalent of the \symbol{__FILE__} and \symbol{__LINE__} \acronym{ANSI} C preprocessor macros? How do I find out where an error occurred?
-
-There is no direct equivalent of \symbol{__FILE__} and
-\symbol{__LINE__} in ANSI Common Lisp; this is perhaps most simply
-explained by the fact that CL is not particularly a file-oriented and
-definitely not a line-oriented language. That said, your particular
-implementation may carry around some information about where functions
-were compiled, and \code{COMPILE-FILE} binds the special variables
-\code{*COMPILE-FILE-TRUENAME*} and \code{*COMPILE-FILE-PATHNAME*}.
-
- (defun foo () (break "Stopped inside ~S" (the-function-i-am-in)))
-
- (setf (symbol-function 'bar) (symbol-function 'foo))
-
- (bar)
-
-
-Are you in a breakpoint in FOO or in BAR?
-
*** Why isn't there a DEEP-COPY function in the language?
Copying an arbitrary structure or object needs context to determine
@@ -118,75 +99,6 @@
(flet ((square (x) (make-instance 'square :area (squarex)))) ...)
-*** Where can I find free lisp compilers or interpreters?
-
-There are a number of free (in both the `gratis' and the `libre' senses) lisp environments:
-
-\b{\link{\href{http://clisp.cons.org/}\text{CLISP}}}
-
-A lightweight common lisp interpreter and compiler, which compiles to
-bytecode, and runs on Windows, AmigaOS, Acorns, OS/2 and most flavours
-of Unix. CLISP is licensed under the GNU GPL.}}}
-
-\b{\link{\href{http://www.cons.org/cmucl/}\text{CMUCL}}}
-
-An interpreter and optimizing compiler to native code running on a few
-flavours of Unix (including x86/FreeBSD, x86/Linux and sparc/Solaris).
-CMUCL can be difficult to compile; it requires itself to build itself,
-and bootstrapping is an issue. CMUCL is mostly public domain software,
-though portions are under an X-like or BSD-like licence.
-
-\b{\link{\href{http://www.corman.net/CormanLisp.html}\text{Corman Lisp}}}
-
-Corman Lisp is a compiler for Windows 95/98/2000/ME/NT, with
-integration with the Windows API. Corman Lisp is free for personal
-use.
-
-
-\b{\link{\href{http://ecls.sourceforge.net/}\text{ECL}}}
-
-Standing for \productname{Embeddable Common Lisp}, ECL is an
-implementation of Common Lisp running on at least x86, Sparc and PPC
-architectures, under Linux, FreeBSD, Solaris, MacOSX and Windows
-(using the cygwin environment). As well as a bytecode compiler, ECL
-can compile to C. ECL is licensed under the GNU LGPL.
-
-
-\b{\link{\href{http://savannah.gnu.org/projects/gcl/}\text{GCL}}}
-
-\productname{GNU Common Lisp} has languished in the past as a non-ANSI
-compliant Common Lisp; recent times have let it see more developments
-towards supporting the ANSI Common Lisp standard. It cannot (yet) be
-recommended as a Common Lisp, but it is still useful for running
-software written for it (primarily
-\link{\href{http://maxima.sourceforge.net/}\text{Maxima}} and
-\link{\href{http://www.nongnu.org/axiom/index.html}\text{Axiom}}). GCL
-is licensed under the GNU LGPL.
-
-
-\b{\link{\href{http://openmcl.clozure.com/}\text{OpenMCL}}}
-
-OpenMCL is an opensourced Common Lisp implementation derived from MCL
-4.2, and runs on MacOS X and Linux/PowerPC. It includes a bridge to
-the Cocoa framework that allows convenient manipulation of Objective C
-objects in CLOS. OpenMCL is licensed under the GNU LGPL.
-
-
-\b{\link{\href{http://www.poplog.org/}\text{Poplog}}}
-
-Poplog is an incrementally-compiled runtime that includes a Common
-Lisp implementation, an ML implementation and a Prolog implementation,
-all cohabiting in the same image. It is licensed under an
-XFree86-style license. Poplog CL is not actively maintained.
-
-\b{\link{\href{http://sbcl.sourceforge.net/}\text{SBCL}}}
-
-SBCL is a fork from CMUCL aimed at improving the maintainability by
-removing the bootstrapping issues involved in recompiling. It runs on
-many Unix and Unix-like systems (including Mac OS X). SBCL is licensed
-in a similar fashion to CMUCL: mostly in the Public Domain, with some
-BSD-like and MIT-like portions.
-
*** How do I write a "Hello, World!" programme in Lisp?
This is actually a subtle question; not in the respect of computing
@@ -225,34 +137,6 @@
}}\listitem{\para{Home to a number of Common Lisp development projects.}}}}
-*** Where can I buy a commercial lisp system?
-
-There are a fair few commercial vendors of Lisp systems; the following
-are the most active:
-
-\variablelist{\varlistentry{\term{\link{\href{http://www.franz.com/}
-\text{Allegro Common Lisp}
-
-}}\listitem{\para{Franz Inc's Allegro Common Lisp is a fine lisp
- development environment. See their website for more
- details.}}}\varlistentry{\term{\link{\href{http://www.xanalys.com/}
-\text{LCL}
-
-}}\listitem{\para{LCL (formerly Liquid Common Lisp) is an offering from
- Xanalys.}}}\varlistentry{\term{\link{\href{http://www.xanalys.com/}
-\text{LispWorks}
-
-}}\listitem{\para{Another offering from Xanalys, LispWorks has a
- different set of extensions above the ANSI specification
- from LCL.}}}\varlistentry{\term{\link{\href{http://www.digitool.com/}
-\text{MCL}
-
-}}\listitem{\para{A commercial implementation of Common Lisp for the
- Macintosh.} }}\varlistentry{\term{\link{\href{http://www.scieneer.com/}
-\text{Scieneer Pty Ltd}
-
-}}\listitem{\para{A commercial natively multithreaded implementation of
- Common Lisp for various Unixes.}}}\varlistentry{\term{Symbolics Common Lisp}\listitem{\para{} }}}
*** The read-eval-print loop is just sitting there after I've typed in my form. What's happening?
One possible explanation for this behaviour is that you have typed in
@@ -282,6 +166,27 @@
\text{comp.lang.scheme}}, where discussion would be much more welcome
and appropriate.
+
+** Possibly obsolete
+
+*** What is the Lisp equivalent of the \symbol{__FILE__} and \symbol{__LINE__} \acronym{ANSI} C preprocessor macros? How do I find out where an error occurred?
+
+There is no direct equivalent of \symbol{__FILE__} and
+\symbol{__LINE__} in ANSI Common Lisp; this is perhaps most simply
+explained by the fact that CL is not particularly a file-oriented and
+definitely not a line-oriented language. That said, your particular
+implementation may carry around some information about where functions
+were compiled, and \code{COMPILE-FILE} binds the special variables
+\code{*COMPILE-FILE-TRUENAME*} and \code{*COMPILE-FILE-PATHNAME*}.
+
+ (defun foo () (break "Stopped inside ~S" (the-function-i-am-in)))
+
+ (setf (symbol-function 'bar) (symbol-function 'foo))
+
+ (bar)
+
+
+Are you in a breakpoint in FOO or in BAR?
*** Why are my structure contents wrong?
More information about the cl-faq
mailing list