[0f3198]: history.lisp Maximize Restore History

Download this file

history.lisp    67 lines (62 with data), 3.8 kB

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
(in-package :sbcl-page)
(define-page :history "History and Copyright" "history" history-page)
(defun history-page ()
(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
architecture of the compiler, and much of the runtime support code)
are only slightly changed. Enough changes have been made to the
interface and architecture that calling the new system CMU Common Lisp
would cause confusion - the world does not need multiple incompatible
systems named CMU CL. But it's appropriate to acknowledge the descent
from the CMU hackers (and post-CMU CMU CL hackers) who did most of the
heavy lifting to make the system work. So the system is named Steel
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
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
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
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
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
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
;;;; more information.
;;;;
;;;; This software is derived from the CMU CL system, which was
;;;; written at Carnegie Mellon University and released into the
;;;; public domain. The software is in the public domain and is
;;;; 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")
" 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")
" details individual contributions.")))