headers
codesite | 23 Jul 00:03
Picon
Favicon

[lispfaq commit] r22 - trunk

Author: peter.seibel
Date: Tue Jul 22 15:03:11 2008
New Revision: 22

Modified:
   trunk/faq.txt
   trunk/lispfaq.txt
   trunk/staging-faq.txt

Log:
Another typo and some old unchecked in changes.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Tue Jul 22 15:03:11 2008
@@ -545,12 +545,77 @@

 *** Where is my compiler?  My debugger?  Where is my program running?

-Lisp works quite differently than most languages that you may be
-familiar with, for example C has a very distinct cycle. In the C
-style, you edit some code, compile it with a separate compiler and
-produce an executable.  You can then run that executable, perhaps with
-a debugger attached to it. Modern IDEs smooth the distinctions between
-these steps, but under the hood they are still there.
+When it comes to how you develop and run your software Lisp works
+differently than most other languages that you may be familiar with.
+(Unless you happen to be familiar with Smalltalk, which inherited many
+of its ideas from Lisp.) If you are used to "compiled" languages, for
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 22 Jul 21:53
Picon
Favicon

[lispfaq commit] r21 - in trunk: . code

Author: peter.seibel
Date: Tue Jul 22 12:52:39 2008
New Revision: 21

Modified:
   trunk/code/faq.lisp
   trunk/faq.txt

Log:
Fixing typo.

Modified: trunk/code/faq.lisp
==============================================================================
--- trunk/code/faq.lisp	(original)
+++ trunk/code/faq.lisp	Tue Jul 22 12:52:39 2008
@@ -21,7 +21,8 @@

 (defun render-faq (input &optional output)
   "Generate HTML version of FAQ."
-  (let ((*paragraph-tags* '("modeline")))
+  (let ((*paragraph-tags* '("modeline"))
+	(*parse-links* nil))
     (with-tag-translations ((:cl . (:span :class :cl))
 			    (:datestamp . datestamp)
 			    (:figure . figure))

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Tue Jul 22 12:52:39 2008
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 15 Mar 04:45
Picon
Favicon

[lispfaq commit] r20 - trunk/rhodes-faq

Author: peter.seibel
Date: Wed Mar 14 20:44:57 2007
New Revision: 20

Added:
   trunk/rhodes-faq/
   trunk/rhodes-faq/README
   trunk/rhodes-faq/faq.css
   trunk/rhodes-faq/index.html
   trunk/rhodes-faq/myths.html
   trunk/rhodes-faq/newsgroup.html
   trunk/rhodes-faq/pitfalls.html
   trunk/rhodes-faq/programming.html
   trunk/rhodes-faq/resources.html
   trunk/rhodes-faq/terminology.html

Log:
Christophe Rhodes's FAQ.

Added: trunk/rhodes-faq/README
==============================================================================
--- (empty file)
+++ trunk/rhodes-faq/README	Wed Mar 14 20:44:57 2007
 <at>  <at>  -0,0 +1,3  <at>  <at> 
+This is a snapshot of the HTML version of the old Christophe Rhodes
+FAQ from which we borrowed a few questions (and hacked up versions of
+the answers). With Christophe's blessing.
\ No newline at end of file

Added: trunk/rhodes-faq/faq.css
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 13 Mar 04:50
Picon
Favicon

[lispfaq commit] r19 - trunk

Author: peter.seibel
Date: Mon Mar 12 20:49:51 2007
New Revision: 19

Modified:
   trunk/faq.txt

Log:
Adding new 'Is Scheme a Lisp?' answer.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Mon Mar 12 20:49:51 2007
@@ -121,7 +121,7 @@

   @ \link{\href{http://www.lispworks.com/documentation/HyperSpec/Front/index.htm}\text{The
HyperSpec}}, as appropriate

-Learning why macros are soooo cool / Advanced Lisp:
+Learning why macros are so cool / Advanced Lisp:

   @ \link{\href{http://mitpress.mit.edu/sicp/}\text{Structure and Interpretation of Computer
Programs}} ("SICP") (Actually
     about Scheme, but useful to learn how to think in Lisp)
@@ -143,7 +143,7 @@
   @ \link{\href{http://www.norvig.com/paip.html}\text{Paradigms of Artificial Intelligence
Programming : Case Studies in
   Common Lisp}} ("PAIP")
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 11 Mar 23:35
Picon
Favicon

[lispfaq commit] r18 - trunk

Author: peter.seibel
Date: Sun Mar 11 15:35:31 2007
New Revision: 18

Modified:
   trunk/faq.txt
   trunk/lispfaq.txt

Log:
Moving online resources question from lispfaq to faq. And some other tweaks.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Sun Mar 11 15:35:31 2007
@@ -2,16 +2,17 @@

 * Common Lisp FAQ 

-\i{This is the beginning of what what we hope will become the
-canonical Common Lisp FAQ. Or, possibly, it the result of yet another
-in the seemingly endless series of efforts to produce such a canonical
-FAQ that will, like the others, fizzle after an initial burst of
-energy devoted largely to converting parts of older FAQs into some new
-better format. There has been on-again, off-again effort on this FAQ
-which is--as of 7 March 2007--on again. If you have questions or
-suggestions email
\link{\href{mailto:peter@...}\text{peter@...}}
or see
-\url{http://wiki.alu.org/Common_Lisp_FAQ} for more information on the
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 11 Mar 22:33
Picon
Favicon

[lispfaq commit] r17 - trunk

Author: peter.seibel
Date: Sun Mar 11 14:33:08 2007
New Revision: 17

Modified:
   trunk/faq.txt
   trunk/lispfaq.txt

Log:
Moving stuck repl question from lispfaq to faq and rewriting benevolent dictator answer.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Sun Mar 11 14:33:08 2007
@@ -223,12 +223,12 @@

 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
+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).
+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).
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 11 Mar 01:53
Picon
Favicon

[lispfaq commit] r16 - trunk

Author: peter.seibel
Date: Sat Mar 10 16:53:02 2007
New Revision: 16

Modified:
   trunk/faq.txt

Log:
Fixing typo.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Sat Mar 10 16:53:02 2007
@@ -812,7 +812,7 @@

 \b{CLISP} -- A particular Common Lisp implementation written by Bruno
 Habile. Experienced Common Lispers refer to the language in general as
-CL \i{not} CLISP because it would be to confusing otherwise.
+CL \i{not} CLISP because it would be too confusing otherwise.

 \b{CMUCL} -- Carnegie Mellon University Common Lisp. A well regarded
 Common Lisp implementation originally developed at Carnegie Mellon.
Permalink | Reply | 0 comments |
headers
codesite | 8 Mar 20:56
Picon
Favicon

[lispfaq commit] r15 - trunk

Author: peter.seibel
Date: Thu Mar  8 11:56:06 2007
New Revision: 15

Modified:
   trunk/faq.txt

Log:
Updating implementation lists some.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Thu Mar  8 11:56:06 2007
@@ -133,11 +133,22 @@
 There are a number of free (in both the "gratis" and the "libre"
 senses) Lisp environments:

+\b{link{\href{}\text{ABCL}}}
+
+ABCL (Armed Bear Common Lisp) is an implementation of ANSI Common Lisp
+that runs in a Java virtual machine. It provides a runtime system, a
+compiler that compiles Lisp source to JVM bytecode, and an interactive
+REPL for program development. It runs on any platform that support
+Java 1.4 (or later), including Linux, Windows, and Mac OS X. It is, by
+the author's admission, a relatively young implementation, and has
+some notable limitations in its CLOS implementation. ABCL is licensed
+under the GNU GPL, with a special linking exception.
+
 \b{\link{\href{http://clisp.cons.org/}\text{CLISP}}}
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 8 Mar 20:38
Picon
Favicon

[lispfaq commit] r14 - trunk

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.
+
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 8 Mar 19:17
Picon
Favicon

[lispfaq commit] r13 - trunk

Author: peter.seibel
Date: Thu Mar  8 10:17:23 2007
New Revision: 13

Modified:
   trunk/faq.txt
   trunk/lispfaq.txt

Log:
Moving string splitting question from lispfaq to faq.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Thu Mar  8 10:17:23 2007
@@ -511,7 +511,7 @@

 ** Nomenclature

-*** Why is it called "LET"?
+*** Why is it called LET?

 Think of a mathematical proof - "Let x be the distance from origin ..."

@@ -823,6 +823,33 @@

     (map-into (make-array 10) #'make-foo)

+
+*** How do I split a string?
(Continue reading)

Permalink | Reply | 0 comments |
headers
codesite | 8 Mar 07:20
Picon
Favicon

[lispfaq commit] r12 - trunk

Author: peter.seibel
Date: Wed Mar  7 22:20:05 2007
New Revision: 12

Modified:
   trunk/faq.txt
   trunk/lispfaq.txt

Log:
Reorging lispfaq a bit and moving READ-FROM-STRING question into faq.

Modified: trunk/faq.txt
==============================================================================
--- trunk/faq.txt	(original)
+++ trunk/faq.txt	Wed Mar  7 22:20:05 2007
@@ -824,6 +824,28 @@
     (map-into (make-array 10) #'make-foo)

 
+*** Why does (read-from-string "foobar" :start 3) return FOOBAR instead of BAR?
+
+\cl{READ-FROM-STRING} is one of the rare functions that takes both
+\code{&optional} and \code{&key} arguments. The complete argument list is:
+
+    string &optional eof-error-p eof-value &key :start :end :preserve-whitespace
+
+When a function takes both types of arguments, all the optional
+arguments must be specified explicitly before any of the keyword
+arguments may be specified. In the example above, :\code{start}
+becomes the value of the optional \code{eof-error-p} parameter and 3
(Continue reading)

Permalink | Reply | 0 comments |

Gmane