Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Diff of /history.lisp [4e5d73] .. [f3064f] Maximize Restore

  Switch to side-by-side view

--- a/history.lisp
+++ b/history.lisp
@@ -1,10 +1,14 @@
+(in-package :sbcl-page)
+
 (define-page :history "History and Copyright" "history" history-page)
 
 (defun history-page ()
-  `((:|h2| "Origins of SBCL and its name")
-    (:|p|
-     "SBCL derives most of its code from " ((:|a| :|href|
-"http://www.cons.org/cmucl/") "CMU CL") ", created at Carnegie Mellon
+  (list
+   (<h2> "Origins of SBCL and its name")
+   (<p>
+    "SBCL derives most of its code from "
+    (<a href= "http://www.cons.org/cmucl/"> "CMU CL")
+    ", created at Carnegie Mellon
 University. Radical changes have been made to some parts of the system
  (particularly bootstrapping) but many fundamentals (like the mapping
 of Lisp abstractions onto the underlying hardware, the basic
@@ -18,34 +22,36 @@
 Bank after the industries where Andrew Carnegie and Andrew Mellon,
 respectively, made the big bucks.")
 
-    (:|h2| "Relationship with CMUCL")
-    (:|p| "In December 1999, SBCL forked off the main branch of
+   (<h2> "Relationship with CMUCL")
+   (<p>
+    "In December 1999, SBCL forked off the main branch of
 CMUCL. Broadly speaking, SBCL is distinguished from CMU CL by a
 greater emphasis on maintainability."
-     (:|ul|
-      (:|li| "The compiled SBCL system corresponds to the source code
+    (<ul>
+     (<li>
+      "The compiled SBCL system corresponds to the source code
 in a controlled, verifiable way, and arbitrary changes can be made to
 the system without causing bootstrapping problems.")
-      (:|li| "Anyone can build the system routinely, even from an unrelated system like OpenMCL.")
-      (:|li| "The system is simpler, in part because we've gotten rid of old CMU CL extensions which contributed lots of special cases (like the byte compiler/interpreter), and in part because we've actively hunted down and refactored unnecessarily complex code (especially code which was reused by cutting and pasting)."))
-     "CMUCL and SBCL each have their own unique set of features: for instance, SBCL features native machine threads on Linux/x86 (CMU has userspace threads), and CMUCL has the generational garbage collector on SPARC/Solaris. But in general the user-visible difference isn't huge, since most visible bug fixes and improvements are actively ported between the two systems.")
-
-    (:|h2| "License information")
-    (:|p| "SBCL is derived from CMU CL, and carries the same licensing
+     (<li> "Anyone can build the system routinely, even from an unrelated system like OpenMCL.")
+     (<li> "The system is simpler, in part because we've gotten rid of old CMU CL extensions which contributed lots of special cases (like the byte compiler/interpreter), and in part because we've actively hunted down and refactored unnecessarily complex code (especially code which was reused by cutting and pasting)."))
+    "CMUCL and SBCL each have their own unique set of features: for instance, SBCL features native machine threads on Linux/x86 (CMU has userspace threads), and CMUCL has the generational garbage collector on SPARC/Solaris. But in general the user-visible difference isn't huge, since most visible bug fixes and improvements are actively ported between the two systems.")
+   
+   (<h2> "License information")
+   (<p> "SBCL is derived from CMU CL, and carries the same licensing
 terms, a mixture of BSD-style (for a few subsystems) and public domain
  (for the rest of the system).")
-    (:|p| "Some of the files in CMU CL have a BSD-style license
+   (<p> "Some of the files in CMU CL have a BSD-style license
 requiring that credit be given to the institutions which owned
 the copyright to the original versions: Xerox, Inc., the
 Massachusetts Institute of Technology, Symbolics, Inc., and Gerd
 Moellmann. For these files, SBCL necessarily uses the same
 BSD-style license as CMU CL did.")
-    (:|p|
-     "The rest of the files in SBCL (as in CMU CL) are in the public
+   (<p>
+    "The rest of the files in SBCL (as in CMU CL) are in the public
 domain. The boilerplate at the beginning of SBCL source files looks
 like this:"
-     (:|pre|
-      ";;;; This software is part of the SBCL system. See the README file for
+    (<pre>
+     ";;;; This software is part of the SBCL system. See the README file for
 ;;;; more information.
 ;;;;
 ;;;; This software is derived from the CMU CL system, which was
@@ -54,9 +60,7 @@
 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
 ;;;; files for more information.")
      "The " 
-     ((:|a| :|href| "http://sbcl.cvs.sourceforge.net/*checkout*/sbcl/sbcl/COPYING?revision=HEAD")
-      "COPYING")
+     (<a href= "http://sbcl.cvs.sourceforge.net/*checkout*/sbcl/sbcl/COPYING?revision=HEAD"> "COPYING")
      " file discusses further the particular licenses of parts of SBCL, whereas " 
-     ((:|a| :|href| "http://sbcl.cvs.sourceforge.net/*checkout*/sbcl/sbcl/CREDITS?revision=HEAD")
-      "CREDITS")
+     (<a href= "http://sbcl.cvs.sourceforge.net/*checkout*/sbcl/sbcl/CREDITS?revision=HEAD"> "CREDITS")
      " details individual contributions.")))