Commit 43100650 authored by mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f's avatar mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f
Browse files

Documentation & metadata updates prior to abcl-1.3.0 branch.

parent 37d3a6bd
......@@ -51,7 +51,7 @@ following command:
which should result in output like the following
Armed Bear Common Lisp 1.3.0
Java 1.6.0_21 Sun Microsystems Inc.
Java 1.7.0_51 Sun Microsystems Inc.
Java HotSpot(TM) Client VM
Low-level initialization completed in 0.3 seconds.
Startup completed in 2.294 seconds.
......@@ -67,7 +67,7 @@ preferred (and most tested way) is to being to use the Ant build tool:
* Use the Ant build tool for Java environments.
* Use the NetBeans [67].x IDE to open ABCL as a project.
* Use the NetBeans [678].x IDE to open ABCL as a project.
* Bootstrap ABCL using a Common Lisp implementation. Supported
implementations for this process: SBCL, CMUCL, OpenMCL, Allegro
......@@ -109,9 +109,11 @@ Using NetBeans
Obtain and install the [NetBeans IDE][2]. One should be able to open
the ABCL directory as a project in the Netbeans 6.x application,
whereupon the usual build, run, and debug targets as invoked in the
GUI are available.
the ABCL directory as a project in the Netbeans application, whereupon
the usual build, run, and debug targets as invoked in the GUI are
available. Use the 'slime' config with a suitably linked 'swank.asd'
in '~/.asdf-install-dir/systems/' to connect a REPL to the NetBeans
debug process.
......@@ -131,7 +133,7 @@ situation, paying attention to the comments in the file. The critical
step is to have Lisp special variable '*JDK*' point to the root of the
Java Development Kit. Underneath the directory referenced by the
value of '*JDK*' there should be an executable Java compiler in
'bin/javac' ('bin/java.exe' under Windows).
'bin/javac' ('bin/javac.exe' under Windows).
Then, one may either use the '' shell script or load
the necessary files into your Lisp image by hand.
......@@ -186,7 +188,7 @@ Because of this,
### Tests
ABCL 1.3.0 now fails only 1[4-6] out of 21708 total tests in the ANSI CL
ABCL 1.3.0 now fails only 1[2-4] out of 21708 total tests in the ANSI CL
test suite (derived from the tests originally written for GCL).
Maxima's test suite runs without failures.
......@@ -17,12 +17,14 @@
@prefix dc: <> .
abcl:branch <> ;
dc:identifier <> ;
dc:identifier <> ;
doap:language "Common Lisp" ;
dc:created "01-JAN-2004" ;
dc:modified "01-JAN-2014" ;
dc:modified "27-JAN-2014" ;
dc:version "abcl-1.3.0" ;
abcl:release "dev" .
abcl:release "dev" ;
abcl:release-candidate "rc-0" .
rdfs:seeAlso <file:README> ;
......@@ -75,7 +77,7 @@ _:user dc:identifier <> ;
dc:license <> ;
dc:license <> ;
rdfs:seeAlso <> ;
rdfs:seeAlso <> ;
dc:licenseDocument <file:COPYING> ;
<> ;
......@@ -93,6 +95,9 @@ doap:Project rdfs:seeAlso [
rdf:_2 <> ;
rdf:_3 <> ;
rdf:_3 <>
rdf:_4 <>
] ;
] .
......@@ -3,7 +3,7 @@
(asdf:defsystem :abcl-asdf
:author "Mark Evenson"
:version "1.3.0"
:description "<> asdf:defsystem <>"
:description "<> asdf:defsystem <>"
:depends-on (jss)
((:module packages :pathname ""
......@@ -13,7 +13,7 @@
#+:sbcl :depends-on
#+:sbcl (sb-bsd-sockets)
:version ""
:description "<> asdf:defsystem <>"
:description "<> asdf:defsystem <>"
:author "Dan Barlow <>, Edi Weitz <> and many others. See the file COPYRIGHT for more details."
:maintainer "Gary Warren King <> // ABCL <> ."
:components ((:file "defpackage")
......@@ -4,7 +4,7 @@
(defsystem :asdf-jar
:author "Mark Evenson"
:version "0.2.1"
:description "<> asdf:defsystem <>"
:description "<> asdf:defsystem <>"
((:module base :pathname "" :components
((:file "asdf-jar")
......@@ -7,6 +7,6 @@
;;; Requires integration with IntelliJ IDEA editor (free download)
(asdf:defsystem jfli-intellij-tests
:version "0.1.0"
:description "<> asdf:defsystem <> ."
:description "<> asdf:defsystem <> ."
:components ((:module test
:components ((:file "yanking")))))
;;;; -*- Mode: LISP -*-
(asdf:defsystem :jss
:author "Alan Ruttenberg, Mark Evenson"
:version "3.0.6"
:description "<> asdf:defsystem <"
:version "3.0.7"
:description "<> asdf:defsystem <"
:components ((:module base
:pathname "" :serial t
:components ((:file "packages")
......@@ -3,7 +3,7 @@
;;;; Need to have jna.jar present for CFFI to work.
(asdf:defsystem :jna
:version "4.0.0"
:description "<> asdf:defsystem <>"
:description "<> asdf:defsystem <>"
:defsystem-depends-on (jss abcl-asdf)
:components ((:mvn ""
:alternate-uri ""
......@@ -13,7 +13,7 @@
<name>Armed Bear Common Lisp (ABCL) Contribs</name>
<description>Extra packages--contribs--for ABCL</description>
......@@ -9,7 +9,7 @@
(defsystem :quicklisp-abcl
"Load Quicklisp from the network if it isn't already installed. <>"
"Load Quicklisp from the network if it isn't already installed. <>"
:version "0.2.0"
:components nil)
......@@ -8,15 +8,24 @@
\title{Armed Bear Common Lisp User Manual}
\date{Version 1.2.0-dev\\
\date{Version 1.3.0-dev\\
March 2, 2013}
January 27, 2014}
\author{Mark Evenson \and Erik H\"{u}lsmann \and Rudolf Schlatte \and
Alessio Stalla \and Ville Voutilainen}
\subsection{Preface to the Third Edition}
\textsc{ABCL} 1.3 now implements a lazily-created LispStack --The Mgmt.
%%Preface to the Third edition, abcl-1.2.
\subsection{Preface to the Third Edition}
The implementation now contains a performant and conformant
implementation of (A)MOP to the point of inclusion in CLOSER-MOP's
test suite.
%%Preface to the second edition, abcl-1.1.
......@@ -42,6 +51,13 @@ code and libraries:
\item \code{jinterface-implementation} creates Lisp-side implementations
of Java interfaces that can be used as listeners for Swing classes and
\item \code{java:jnew-runtime-class} can inject fully synthetic Java
classes--and their objects-- into the current JVM process whose
behavior is specified via closures expressed in Common Lisp.. \footnote{Parts of
the current implementation are not fully finished, so the status
of some interfaces here should be treated with skepticism if you
run into problems.}
\textsc{ABCL} is supported by the Lisp library manager
\textsc{QuickLisp}\footnote{\url{}} and can run many of the
......@@ -113,7 +129,7 @@ contemporary Common Lisp.
\textsc{ABCL} is licensed under the terms of the \textsc{GPL} v2 of
June 1991 with the ``classpath-exception'' (see the file
\texttt{COPYING} in the source distribution \footnote{See
\url{}} for
\url{}} for
the license, term 13 in the same file for the classpath exception).
This license broadly means that you must distribute the sources to
ABCL, including any changes you make, together with a program that
......@@ -138,7 +154,7 @@ course.
\textsc{ABCL} is packaged as a single jar file usually named either
\texttt{abcl.jar} or possibly something like \texttt{abcl-1.2.0.jar} if
\texttt{abcl.jar} or possibly something like \texttt{abcl-1.3.0.jar} if
using a versioned package on the local filesystem from your system
vendor. This jar file can be executed from the command line to obtain a
\textsc{REPL}\footnote{Read-Eval Print Loop, a Lisp command-line}, viz:
......@@ -873,7 +889,7 @@ following caveats:
cannot be the target of write operations.
\item Any results of canonicalization procesures performed on the
\item Any results of canonicalization procedures performed on the
underlying \textsc{URI} are discarded between resolutions (i.e. the
implementation does not attempt to cache the results of current name
resolution of the representing resource unless it is requested to be
......@@ -882,7 +898,7 @@ following caveats:
discarded. Users may programatically initiate a new, local
computation of the resolution of the resource by applying the
\code{CL:TRUENAME} function to a \code{EXT:URL-PATHNAME} object.
Depending on the reliablity and properties of your local
Depending on the reliability and properties of your local
\textsc{REST} infrastructure, these results may not necessarily be
idempotent over time\footnote {See \cite{evenson2011} for the draft
of the publication of the technical details}.
......@@ -908,7 +924,7 @@ In order to ``smooth over'' the bit about types being \code{CL:READ}
from \code{CL:PATHNAME} components, we extend the semantics for the
usual PATHNAME merge semantics when \code{*DEFAULT-PATHNAME-DEFAULTS*}
contains a \code{EXT:JAR-PATHNAME} with the ``do what I mean''
algorithim described in \ref{section:conformance} on page
algorithm described in \ref{section:conformance} on page
%See \ref{_:quicklisp} on page \pageref{_:quicklisp}.
......@@ -927,9 +943,9 @@ expect the following:
the entries containing \code{CL:PATHNAME} objects which describe the
outer and (possibly inner) locations of the jar
archive \footnote{The case of inner and outer
\code{EXT:EJAR-PATHNAME} arises when zip archives themselves
contain zip archives which is the case when the ABCL fasl is
included in the abcl.jar zip archive.}.
\code{EXT:JAR-PATHNAME} \ref{EXT:JAR-PATHNAME} arises when zip
archives themselves contain zip archives which is the case when
the ABCL fasl is included in the abcl.jar zip archive.}.
\item A \code{EXT:URL-PATHNAME} always has a \code{HOST} component that is a
property list. The values of the \code{HOST} property list are
......@@ -943,7 +959,7 @@ expect the following:
\item In order to encapsulate the implementation decisions for these
meanings, the following functions provide a setf-able API for
meanings, the following functions provide a SETF-able API for
reading and writing such values: \code{URL-PATHNAME-QUERY},
\code{URL-PATHNAME-SCHEME}. The specific subtype of a Pathname may
......@@ -1008,7 +1024,7 @@ Example:
--- Function: \textbf{package-local-nicknames} [\textbf{ext}] \textit{package-designator}
Returns an alist of \code{(local-nickname . actual-package)}
Returns an ALIST of \code{(local-nickname . actual-package)}
describing the nicknames local to the designated package.
When in the designated package, calls to \code{find-package} with any
......@@ -1230,7 +1246,7 @@ reader in the definition of the \code{SHARPSIGN-DOUBLE-QUOTE}
asdf-2.30 (see \cite{asdf}) is packaged as core component of \textsc{ABCL},
asdf- (see \cite{asdf}) is packaged as core component of \textsc{ABCL},
but not initialized by default, as it relies on the \textsc{CLOS} subsystem
which can take a bit of time to start \footnote{While this time is
``merely'' on the order of seconds for contemporary 2011 machines,
......@@ -1247,7 +1263,7 @@ CL-USER> (require 'asdf)
The \textsc{ABCL} contrib is packaged as a separate jar archive usually named
\code{abcl-contrib.jar} or possibly something like
\code{abcl-contrib-1.2.0.jar}. The contrib jar is not loaded by the
\code{abcl-contrib-1.3.0.jar}. The contrib jar is not loaded by the
implementation by default, and must be first intialized by the
\code{REQUIRE} mechanism before using any specific contrib:
......@@ -1334,7 +1350,7 @@ Notice that all recursive dependencies have been located and installed
locally from the network as well.
More extensive documentations and examples can be found at
......@@ -1346,7 +1362,7 @@ this package will recursively package all the required source and
fasls in a jar archive.
The documentation for this contrib can be found at
......@@ -1382,14 +1398,14 @@ CL-USER) (#"propertyNames" (#"getProperties" 'java.lang.System))
\end{listing-lisp} %$ <-- un-confuse Emacs font-lock
Some more information on jss can be found in its documentation at
The contrib contains a pure-Java version of JFLI.
......@@ -1404,7 +1420,7 @@ the value of the \textsc{ASDF} central registry in
stashing \textsc{ABCL} specific system definitions for convenient
......@@ -1433,16 +1449,22 @@ In December 2012, we revised the implementation by adding
\textsc{(A)MOP} with the release of abcl-1.1.0. We released
abcl-1.1.1 as a maintainence release on Feburary 14, 2013.
At the beginning of June 2013, we enhanced the stability of the
implementation with the release of abcl-1.2.1.
In January 2014, we introduced the Third Edition of the implementation
with abcl-1.3.0.
\chapter{The MOP Dictionary}
\chapter{The SYSTEM Dictionary}
The public interfaces in this package are subject to change with
\textsc{ABCL} 1.2.
\textsc{ABCL} 1.4.
......@@ -13,7 +13,7 @@
<name>ABCL - Armed Bear Common Lisp</name>
<description>Common Lisp implementation running on the JVM</description>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment